]> Git Repo - binutils.git/blame - gdb/frame.h
2003-01-18 Andrew Cagney <[email protected]>
[binutils.git] / gdb / frame.h
CommitLineData
c906108c 1/* Definitions for dealing with stack frames, for GDB, the GNU debugger.
7cc19214
AC
2
3 Copyright 1986, 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1996,
51603483 4 1997, 1998, 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
c906108c 5
c5aa993b 6 This file is part of GDB.
c906108c 7
c5aa993b
JM
8 This program is free software; you can redistribute it and/or modify
9 it under the terms of the GNU General Public License as published by
10 the Free Software Foundation; either version 2 of the License, or
11 (at your option) any later version.
c906108c 12
c5aa993b
JM
13 This program is distributed in the hope that it will be useful,
14 but WITHOUT ANY WARRANTY; without even the implied warranty of
15 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16 GNU General Public License for more details.
c906108c 17
c5aa993b
JM
18 You should have received a copy of the GNU General Public License
19 along with this program; if not, write to the Free Software
20 Foundation, Inc., 59 Temple Place - Suite 330,
21 Boston, MA 02111-1307, USA. */
c906108c
SS
22
23#if !defined (FRAME_H)
24#define FRAME_H 1
25
1058bca7
AC
26struct symtab_and_line;
27
c97eb5d9
AC
28/* The frame object. */
29
30struct frame_info;
31
32/* The frame object's ID. This provides a per-frame unique identifier
33 that can be used to relocate a `struct frame_info' after a target
7a424e99
AC
34 resume or a frame cache destruct. It of course assumes that the
35 inferior hasn't unwound the stack past that frame. */
c97eb5d9
AC
36
37struct frame_id
38{
39 /* The frame's address. This should be constant through out the
40 lifetime of a frame. */
41 /* NOTE: cagney/2002-11-16: The ia64 has two stacks and hence two
42 frame bases. This will need to be expanded to accomodate that. */
43 CORE_ADDR base;
44 /* The frame's current PC. While the PC within the function may
45 change, the function that contains the PC does not. Should this
46 instead be the frame's function? */
47 CORE_ADDR pc;
48};
49
7a424e99
AC
50/* Methods for constructing and comparing Frame IDs.
51
52 NOTE: Given frameless functions A and B, where A calls B (and hence
53 B is inner-to A). The relationships: !eq(A,B); !eq(B,A);
54 !inner(A,B); !inner(B,A); all hold. This is because, while B is
55 inner to A, B is not strictly inner to A (being frameless, they
56 have the same .base value). */
57
58/* For convenience. All fields are zero. */
59extern const struct frame_id null_frame_id;
60
61/* Construct a frame ID. The second parameter isn't yet well defined.
62 It might be the containing function, or the resume PC (see comment
63 above in `struct frame_id')? A func/pc of zero indicates a
64 wildcard (i.e., do not use func in frame ID comparisons). */
65extern struct frame_id frame_id_build (CORE_ADDR base,
66 CORE_ADDR func_or_pc);
67
68/* Returns non-zero when L is a valid frame (a valid frame has a
69 non-zero .base). */
70extern int frame_id_p (struct frame_id l);
71
72/* Returns non-zero when L and R identify the same frame, or, if
73 either L or R have a zero .func, then the same frame base. */
74extern int frame_id_eq (struct frame_id l, struct frame_id r);
75
76/* Returns non-zero when L is strictly inner-than R (they have
77 different frame .bases). Neither L, nor R can be `null'. See note
78 above about frameless functions. */
79extern int frame_id_inner (struct frame_id l, struct frame_id r);
80
81
c97eb5d9
AC
82/* For every stopped thread, GDB tracks two frames: current and
83 selected. Current frame is the inner most frame of the selected
abc0af47
AC
84 thread. Selected frame is the one being examined by the the GDB
85 CLI (selected using `up', `down', ...). The frames are created
86 on-demand (via get_prev_frame()) and then held in a frame cache. */
87/* FIXME: cagney/2002-11-28: Er, there is a lie here. If you do the
88 sequence: `thread 1; up; thread 2; thread 1' you loose thread 1's
89 selected frame. At present GDB only tracks the selected frame of
90 the current thread. But be warned, that might change. */
c97eb5d9
AC
91/* FIXME: cagney/2002-11-14: At any time, only one thread's selected
92 and current frame can be active. Switching threads causes gdb to
93 discard all that cached frame information. Ulgh! Instead, current
94 and selected frame should be bound to a thread. */
95
abc0af47
AC
96/* On demand, create the inner most frame using information found in
97 the inferior. If the inner most frame can't be created, throw an
98 error. */
c97eb5d9
AC
99extern struct frame_info *get_current_frame (void);
100
abc0af47
AC
101/* Invalidates the frame cache (this function should have been called
102 invalidate_cached_frames).
103
104 FIXME: cagney/2002-11-28: The only difference between
105 flush_cached_frames() and reinit_frame_cache() is that the latter
106 explicitly sets the selected frame back to the current frame there
107 isn't any real difference (except that one delays the selection of
6e7f8b9c
AC
108 a new frame). Code can instead simply rely on get_selected_frame()
109 to reinit's the selected frame as needed. As for invalidating the
110 cache, there should be two methods one that reverts the thread's
111 selected frame back to current frame (for when the inferior
112 resumes) and one that does not (for when the user modifies the
113 target invalidating the frame cache). */
c97eb5d9 114extern void flush_cached_frames (void);
c97eb5d9
AC
115extern void reinit_frame_cache (void);
116
6e7f8b9c
AC
117/* On demand, create the selected frame and then return it. If the
118 selected frame can not be created, this function throws an error. */
119/* FIXME: cagney/2002-11-28: At present, when there is no selected
120 frame, this function always returns the current (inner most) frame.
121 It should instead, when a thread has previously had its frame
122 selected (but not resumed) and the frame cache invalidated, find
123 and then return that thread's previously selected frame. */
124extern struct frame_info *get_selected_frame (void);
125
abc0af47
AC
126/* Select a specific frame. NULL, apparently implies re-select the
127 inner most frame. */
128extern void select_frame (struct frame_info *);
129
c97eb5d9
AC
130/* Given a FRAME, return the next (more inner, younger) or previous
131 (more outer, older) frame. */
132extern struct frame_info *get_prev_frame (struct frame_info *);
133extern struct frame_info *get_next_frame (struct frame_info *);
134
135/* Given a frame's ID, relocate the frame. Returns NULL if the frame
136 is not found. */
137extern struct frame_info *frame_find_by_id (struct frame_id id);
138
139/* Base attributes of a frame: */
140
141/* The frame's `resume' address. Where the program will resume in
142 this frame. */
143extern CORE_ADDR get_frame_pc (struct frame_info *);
144
1058bca7
AC
145/* Closely related to the resume address, various symbol table
146 attributes that are determined by the PC. Note that for a normal
147 frame, the PC refers to the resume address after the return, and
148 not the call instruction. In such a case, the address is adjusted
149 so that it (approximatly) identifies the call site (and not return
150 site).
151
152 NOTE: cagney/2002-11-28: The frame cache could be used to cache the
153 computed value. Working on the assumption that the bottle-neck is
154 in the single step code, and that code causes the frame cache to be
155 constantly flushed, caching things in a frame is probably of little
156 benefit. As they say `show us the numbers'.
157
158 NOTE: cagney/2002-11-28: Plenty more where this one came from:
159 find_frame_block(), find_frame_partial_function(),
160 find_frame_symtab(), find_frame_function(). Each will need to be
161 carefully considered to determine if the real intent was for it to
162 apply to the PC or the adjusted PC. */
163extern void find_frame_sal (struct frame_info *frame,
164 struct symtab_and_line *sal);
165
c193f6ac
AC
166/* Return the frame address from FI. Except in the machine-dependent
167 *FRAME* macros, a frame address has no defined meaning other than
168 as a magic cookie which identifies a frame over calls to the
169 inferior (um, SEE NOTE BELOW). The only known exception is
ae45cd16
AC
170 inferior.h (DEPRECATED_PC_IN_CALL_DUMMY) [ON_STACK]; see comments
171 there. You cannot assume that a frame address contains enough
172 information to reconstruct the frame; if you want more than just to
173 identify the frame (e.g. be able to fetch variables relative to
174 that frame), then save the whole struct frame_info (and the next
175 struct frame_info, since the latter is used for fetching variables
176 on some machines) (um, again SEE NOTE BELOW).
c193f6ac
AC
177
178 NOTE: cagney/2002-11-18: Actually, the frame address isn't
179 sufficient for identifying a frame, and the counter examples are
180 wrong!
181
182 Code that needs to (re)identify a frame must use get_frame_id() and
183 frame_find_by_id() (and in the future, a frame_compare() function
184 instead of INNER_THAN()). Two reasons: an architecture (e.g.,
185 ia64) can have more than one frame address (due to multiple stack
186 pointers) (frame ID is going to be expanded to accomodate this);
187 successive frameless function calls can only be differientated by
188 comparing both the frame's base and the frame's enclosing function
189 (frame_find_by_id() is going to be modified to perform this test).
190
ae45cd16
AC
191 The generic dummy frame version of DEPRECATED_PC_IN_CALL_DUMMY() is
192 able to identify a dummy frame using only the PC value. So the
193 frame address is not needed. In fact, most
194 DEPRECATED_PC_IN_CALL_DUMMY() calls now pass zero as the frame/sp
195 values as the caller knows that those values won't be used. Once
196 all architectures are using generic dummy frames,
197 DEPRECATED_PC_IN_CALL_DUMMY() can drop the sp/frame parameters.
c193f6ac
AC
198 When it comes to finding a dummy frame, the next frame's frame ID
199 (with out duing an unwind) can be used (ok, could if it wasn't for
200 the need to change the way the PPC defined frame base in a strange
201 way).
202
203 Modern architectures should be using something like dwarf2's
204 location expression to describe where a variable lives. Such
205 expressions specify their own debug info centric frame address.
206 Consequently, a generic frame address is pretty meaningless. */
207
208extern CORE_ADDR get_frame_base (struct frame_info *);
209
c97eb5d9 210/* Return the per-frame unique identifer. Can be used to relocate a
7a424e99
AC
211 frame after a frame cache flush (and other similar operations). If
212 FI is NULL, return the null_frame_id. */
213extern struct frame_id get_frame_id (struct frame_info *fi);
c97eb5d9
AC
214
215/* The frame's level: 0 for innermost, 1 for its caller, ...; or -1
216 for an invalid frame). */
217extern int frame_relative_level (struct frame_info *fi);
218
5a203e44
AC
219/* Return the frame's type. Some are real, some are signal
220 trampolines, and some are completly artificial (dummy). */
221
222enum frame_type
223{
224 /* A true stack frame, created by the target program during normal
225 execution. */
226 NORMAL_FRAME,
227 /* A fake frame, created by GDB when performing an inferior function
228 call. */
229 DUMMY_FRAME,
230 /* In a signal handler, various OSs handle this in various ways.
231 The main thing is that the frame may be far from normal. */
232 SIGTRAMP_FRAME
233};
234extern enum frame_type get_frame_type (struct frame_info *);
235
236/* FIXME: cagney/2002-11-10: Some targets want to directly mark a
237 frame as being of a specific type. This shouldn't be necessary.
ae45cd16
AC
238 PC_IN_SIGTRAMP() indicates a SIGTRAMP_FRAME and
239 DEPRECATED_PC_IN_CALL_DUMMY() indicates a DUMMY_FRAME. I suspect
240 the real problem here is that get_prev_frame() only sets
241 initialized after INIT_EXTRA_FRAME_INFO as been called.
242 Consequently, some targets found that the frame's type was wrong
243 and tried to fix it. The correct fix is to modify get_prev_frame()
244 so that it initializes the frame's type before calling any other
245 functions. */
5a203e44
AC
246extern void deprecated_set_frame_type (struct frame_info *,
247 enum frame_type type);
248
c97eb5d9
AC
249/* Unwind the stack frame so that the value of REGNUM, in the previous
250 (up, older) frame is returned. If VALUEP is NULL, don't
251 fetch/compute the value. Instead just return the location of the
252 value. */
253extern void frame_register_unwind (struct frame_info *frame, int regnum,
254 int *optimizedp, enum lval_type *lvalp,
255 CORE_ADDR *addrp, int *realnump,
256 void *valuep);
257
258/* More convenient interface to frame_register_unwind(). */
259/* NOTE: cagney/2002-09-13: Return void as one day these functions may
260 be changed to return an indication that the read succeeded. */
261
262extern void frame_unwind_signed_register (struct frame_info *frame,
263 int regnum, LONGEST *val);
264
265extern void frame_unwind_unsigned_register (struct frame_info *frame,
266 int regnum, ULONGEST *val);
267
268/* Get the value of the register that belongs to this FRAME. This
269 function is a wrapper to the call sequence ``frame_unwind_register
270 (get_next_frame (FRAME))''. As per frame_register_unwind(), if
271 VALUEP is NULL, the registers value is not fetched/computed. */
272
273extern void frame_register (struct frame_info *frame, int regnum,
274 int *optimizedp, enum lval_type *lvalp,
275 CORE_ADDR *addrp, int *realnump,
276 void *valuep);
277
278/* More convenient interface to frame_register(). */
279/* NOTE: cagney/2002-09-13: Return void as one day these functions may
280 be changed to return an indication that the read succeeded. */
281
282extern void frame_read_signed_register (struct frame_info *frame,
283 int regnum, LONGEST *val);
284
285extern void frame_read_unsigned_register (struct frame_info *frame,
286 int regnum, ULONGEST *val);
287
288/* Map between a frame register number and its name. A frame register
289 space is a superset of the cooked register space --- it also
290 includes builtin registers. */
291
292extern int frame_map_name_to_regnum (const char *name, int strlen);
293extern const char *frame_map_regnum_to_name (int regnum);
294
f18c5a73
AC
295/* Unwind the PC. Strictly speaking return the resume address of the
296 calling frame. For GDB, `pc' is the resume address and not a
297 specific register. */
298
299extern CORE_ADDR frame_pc_unwind (struct frame_info *frame);
300
c689142b
AC
301/* Unwind the frame ID. Return an ID that uniquely identifies the
302 caller's frame. */
303extern struct frame_id frame_id_unwind (struct frame_info *frame);
304
c97eb5d9 305\f
4f460812
AC
306/* Return the location (and possibly value) of REGNUM for the previous
307 (older, up) frame. All parameters except VALUEP can be assumed to
308 be non NULL. When VALUEP is NULL, just the location of the
309 register should be returned.
310
311 UNWIND_CACHE is provided as mechanism for implementing a per-frame
312 local cache. It's initial value being NULL. Memory for that cache
479ab5a0 313 should be allocated using frame_obstack_zalloc().
4f460812
AC
314
315 Register window architectures (eg SPARC) should note that REGNUM
316 identifies the register for the previous frame. For instance, a
317 request for the value of "o1" for the previous frame would be found
318 in the register "i1" in this FRAME. */
319
320typedef void (frame_register_unwind_ftype) (struct frame_info *frame,
321 void **unwind_cache,
322 int regnum,
323 int *optimized,
324 enum lval_type *lvalp,
325 CORE_ADDR *addrp,
326 int *realnump,
327 void *valuep);
328
f18c5a73
AC
329/* Same as for registers above, but return the address at which the
330 calling frame would resume. */
331
332typedef CORE_ADDR (frame_pc_unwind_ftype) (struct frame_info *frame,
333 void **unwind_cache);
334
c689142b
AC
335/* Same as for registers above, but return the ID of the frame that
336 called this one. */
337
c170fb60
AC
338typedef void (frame_id_unwind_ftype) (struct frame_info *frame,
339 void **unwind_cache,
340 struct frame_id *id);
c689142b 341
c906108c
SS
342/* Describe the saved registers of a frame. */
343
344#if defined (EXTRA_FRAME_INFO) || defined (FRAME_FIND_SAVED_REGS)
345/* XXXX - deprecated */
346struct frame_saved_regs
347 {
c2c6d25f
JM
348 /* For each register R (except the SP), regs[R] is the address at
349 which it was saved on entry to the frame, or zero if it was not
350 saved on entry to this frame. This includes special registers
351 such as pc and fp saved in special ways in the stack frame.
c906108c 352
c2c6d25f
JM
353 regs[SP_REGNUM] is different. It holds the actual SP, not the
354 address at which it was saved. */
c906108c
SS
355
356 CORE_ADDR regs[NUM_REGS];
357 };
358#endif
359
360/* We keep a cache of stack frames, each of which is a "struct
361 frame_info". The innermost one gets allocated (in
362 wait_for_inferior) each time the inferior stops; current_frame
363 points to it. Additional frames get allocated (in
7a292a7a 364 get_prev_frame) as needed, and are chained through the next
c906108c
SS
365 and prev fields. Any time that the frame cache becomes invalid
366 (most notably when we execute something, but also if we change how
367 we interpret the frames (e.g. "set heuristic-fence-post" in
368 mips-tdep.c, or anything which reads new symbols)), we should call
369 reinit_frame_cache. */
370
371struct frame_info
372 {
c193f6ac
AC
373 /* Nominal address of the frame described. See comments at
374 get_frame_base() about what this means outside the *FRAME*
375 macros; in the *FRAME* macros, it can mean whatever makes most
376 sense for this machine. */
c906108c
SS
377 CORE_ADDR frame;
378
379 /* Address at which execution is occurring in this frame.
380 For the innermost frame, it's the current pc.
381 For other frames, it is a pc saved in the next frame. */
382 CORE_ADDR pc;
383
7cc19214
AC
384 /* Level of this frame. The inner-most (youngest) frame is at
385 level 0. As you move towards the outer-most (oldest) frame,
386 the level increases. This is a cached value. It could just as
387 easily be computed by counting back from the selected frame to
388 the inner most frame. */
389 /* NOTE: cagney/2002-04-05: Perhaphs a level of ``-1'' should be
390 reserved to indicate a bogus frame - one that has been created
391 just to keep GDB happy (GDB always needs a frame). For the
392 moment leave this as speculation. */
393 int level;
394
5a203e44
AC
395 /* The frame's type. */
396 enum frame_type type;
c906108c
SS
397
398 /* For each register, address of where it was saved on entry to
399 the frame, or zero if it was not saved on entry to this frame.
400 This includes special registers such as pc and fp saved in
401 special ways in the stack frame. The SP_REGNUM is even more
e8759349
AC
402 special, the address here is the sp for the previous frame, not
403 the address where the sp was saved. */
c906108c
SS
404 /* Allocated by frame_saved_regs_zalloc () which is called /
405 initialized by FRAME_INIT_SAVED_REGS(). */
64485362 406 CORE_ADDR *saved_regs; /*NUM_REGS + NUM_PSEUDO_REGS*/
c906108c
SS
407
408#ifdef EXTRA_FRAME_INFO
409 /* XXXX - deprecated */
410 /* Anything extra for this structure that may have been defined
411 in the machine dependent files. */
c5aa993b 412 EXTRA_FRAME_INFO
c906108c
SS
413#endif
414
415 /* Anything extra for this structure that may have been defined
416 in the machine dependent files. */
479ab5a0 417 /* Allocated by frame_extra_info_zalloc () which is called /
c906108c
SS
418 initialized by INIT_EXTRA_FRAME_INFO */
419 struct frame_extra_info *extra_info;
420
b6af0555
JS
421 /* If dwarf2 unwind frame informations is used, this structure holds all
422 related unwind data. */
cc22880b 423 struct context *context;
b6af0555 424
f18c5a73
AC
425 /* Unwind cache shared between the unwind functions - they had
426 better all agree as to the contents. */
427 void *unwind_cache;
428
429 /* See description above. The previous frame's registers. */
4f460812 430 frame_register_unwind_ftype *register_unwind;
f18c5a73
AC
431
432 /* See description above. The previous frame's resume address.
433 Save the previous PC in a local cache. */
434 frame_pc_unwind_ftype *pc_unwind;
435 int pc_unwind_cache_p;
436 CORE_ADDR pc_unwind_cache;
4f460812 437
c689142b
AC
438 /* See description above. The previous frame's resume address.
439 Save the previous PC in a local cache. */
440 frame_id_unwind_ftype *id_unwind;
441 int id_unwind_cache_p;
442 struct frame_id id_unwind_cache;
443
15220c65
AC
444 /* Pointers to the next (down, inner, younger) and previous (up,
445 outer, older) frame_info's in the frame cache. */
446 struct frame_info *next; /* down, inner, younger */
447 int prev_p;
448 struct frame_info *prev; /* up, outer, older */
c906108c
SS
449 };
450
c5394b80
JM
451/* Values for the source flag to be used in print_frame_info_base(). */
452enum print_what
453 {
454 /* Print only the source line, like in stepi. */
455 SRC_LINE = -1,
456 /* Print only the location, i.e. level, address (sometimes)
457 function, args, file, line, line num. */
458 LOCATION,
459 /* Print both of the above. */
460 SRC_AND_LOC,
461 /* Print location only, but always include the address. */
462 LOC_AND_ADDRESS
463 };
464
64485362
AC
465/* Allocate additional space for appendices to a struct frame_info.
466 NOTE: Much of GDB's code works on the assumption that the allocated
467 saved_regs[] array is the size specified below. If you try to make
468 that array smaller, GDB will happily walk off its end. */
c906108c 469
64485362
AC
470#ifdef SIZEOF_FRAME_SAVED_REGS
471#error "SIZEOF_FRAME_SAVED_REGS can not be re-defined"
c906108c 472#endif
64485362
AC
473#define SIZEOF_FRAME_SAVED_REGS \
474 (sizeof (CORE_ADDR) * (NUM_REGS+NUM_PSEUDO_REGS))
475
479ab5a0
AC
476/* Allocate zero initialized memory from the frame cache obstack.
477 Appendices to the frame info (such as the unwind cache) should
478 allocate memory using this method. */
479
480extern void *frame_obstack_zalloc (unsigned long size);
c906108c 481
51603483
DJ
482/* If FRAME_CHAIN_VALID returns zero it means that the given frame
483 is the outermost one and has no caller. */
c906108c 484
51603483 485extern int frame_chain_valid (CORE_ADDR, struct frame_info *);
c906108c 486
a14ed312 487extern void generic_save_dummy_frame_tos (CORE_ADDR sp);
c906108c 488
c906108c 489
c906108c
SS
490#ifdef FRAME_FIND_SAVED_REGS
491/* XXX - deprecated */
95486978
AC
492#define FRAME_INIT_SAVED_REGS(FI) deprecated_get_frame_saved_regs (FI, NULL)
493extern void deprecated_get_frame_saved_regs (struct frame_info *,
494 struct frame_saved_regs *);
c906108c 495#endif
c5aa993b 496
ae767bfb
JB
497extern struct block *get_frame_block (struct frame_info *,
498 CORE_ADDR *addr_in_block);
c906108c 499
805e2818
AC
500/* Return the `struct block' that belongs to the selected thread's
501 selected frame. If the inferior has no state, return NULL.
502
503 NOTE: cagney/2002-11-29:
504
505 No state? Does the inferior have any execution state (a core file
506 does, an executable does not). At present the code tests
507 `target_has_stack' but I'm left wondering if it should test
508 `target_has_registers' or, even, a merged target_has_state.
509
510 Should it look at the most recently specified SAL? If the target
511 has no state, should this function try to extract a block from the
512 most recently selected SAL? That way `list foo' would give it some
513 sort of reference point. Then again, perhaphs that would confuse
514 things.
515
516 Calls to this function can be broken down into two categories: Code
517 that uses the selected block as an additional, but optional, data
518 point; Code that uses the selected block as a prop, when it should
519 have the relevant frame/block/pc explicitly passed in.
520
521 The latter can be eliminated by correctly parameterizing the code,
522 the former though is more interesting. Per the "address" command,
523 it occures in the CLI code and makes it possible for commands to
524 work, even when the inferior has no state. */
525
ae767bfb 526extern struct block *get_selected_block (CORE_ADDR *addr_in_block);
c906108c 527
a14ed312 528extern struct symbol *get_frame_function (struct frame_info *);
c906108c 529
42f99ac2
JB
530extern CORE_ADDR frame_address_in_block (struct frame_info *);
531
a14ed312 532extern CORE_ADDR get_pc_function_start (CORE_ADDR);
c906108c 533
a14ed312 534extern struct block *block_for_pc (CORE_ADDR);
c906108c 535
a14ed312 536extern struct block *block_for_pc_sect (CORE_ADDR, asection *);
c906108c 537
a14ed312 538extern int frameless_look_for_prologue (struct frame_info *);
c906108c 539
a14ed312
KB
540extern void print_frame_args (struct symbol *, struct frame_info *,
541 int, struct ui_file *);
c906108c 542
a14ed312 543extern struct frame_info *find_relative_frame (struct frame_info *, int *);
c906108c 544
a14ed312
KB
545extern void show_and_print_stack_frame (struct frame_info *fi, int level,
546 int source);
7a292a7a 547
a14ed312 548extern void print_stack_frame (struct frame_info *, int, int);
c906108c 549
a14ed312 550extern void show_stack_frame (struct frame_info *);
c906108c 551
a14ed312 552extern void print_frame_info (struct frame_info *, int, int, int);
c906108c 553
a14ed312 554extern void show_frame_info (struct frame_info *, int, int, int);
c906108c 555
a14ed312 556extern struct frame_info *block_innermost_frame (struct block *);
c906108c 557
135c175f
AC
558/* NOTE: cagney/2002-09-13: There is no need for this function.
559 Instead either of frame_unwind_signed_register() or
560 frame_unwind_unsigned_register() can be used. */
561extern CORE_ADDR deprecated_read_register_dummy (CORE_ADDR pc,
562 CORE_ADDR fp, int);
a14ed312
KB
563extern void generic_push_dummy_frame (void);
564extern void generic_pop_current_frame (void (*)(struct frame_info *));
565extern void generic_pop_dummy_frame (void);
c906108c 566
a14ed312
KB
567extern int generic_pc_in_call_dummy (CORE_ADDR pc,
568 CORE_ADDR sp, CORE_ADDR fp);
da130f98
AC
569
570/* NOTE: cagney/2002-06-26: Targets should no longer use this
571 function. Instead, the contents of a dummy frames registers can be
572 obtained by applying: frame_register_unwind to the dummy frame; or
573 get_saved_register to the next outer frame. */
574
575extern char *deprecated_generic_find_dummy_frame (CORE_ADDR pc, CORE_ADDR fp);
c906108c 576
a14ed312
KB
577extern void generic_fix_call_dummy (char *dummy, CORE_ADDR pc, CORE_ADDR fun,
578 int nargs, struct value **args,
579 struct type *type, int gcc_p);
cce74817 580
bdcdd535
AC
581/* The function generic_get_saved_register() has been made obsolete.
582 GET_SAVED_REGISTER now defaults to the recursive equivalent -
583 generic_unwind_get_saved_register() - so there is no need to even
584 set GET_SAVED_REGISTER. Architectures that need to override the
585 register unwind mechanism should modify frame->unwind(). */
586extern void deprecated_generic_get_saved_register (char *, int *, CORE_ADDR *,
587 struct frame_info *, int,
588 enum lval_type *);
c906108c 589
6096c27a
AC
590extern void generic_save_call_dummy_addr (CORE_ADDR lo, CORE_ADDR hi);
591
60edd51d
AC
592extern void get_saved_register (char *raw_buffer, int *optimized,
593 CORE_ADDR * addrp,
594 struct frame_info *frame,
595 int regnum, enum lval_type *lval);
596
cda5a58a
AC
597extern int frame_register_read (struct frame_info *frame, int regnum,
598 void *buf);
599
36dc181b
EZ
600/* From stack.c. */
601extern void args_info (char *, int);
602
603extern void locals_info (char *, int);
604
605extern void (*selected_frame_level_changed_hook) (int);
606
607extern void return_command (char *, int);
608
abc0af47
AC
609
610/* NOTE: cagney/2002-11-27:
611
612 You might think that the below global can simply be replaced by a
613 call to either get_selected_frame() or select_frame().
614
615 Unfortunatly, it isn't that easy.
616
617 The relevant code needs to be audited to determine if it is
618 possible (or pratical) to instead pass the applicable frame in as a
619 parameter. For instance, DEPRECATED_DO_REGISTERS_INFO() relied on
6e7f8b9c 620 the deprecated_selected_frame global, while its replacement,
abc0af47
AC
621 PRINT_REGISTERS_INFO(), is parameterized with the selected frame.
622 The only real exceptions occure at the edge (in the CLI code) where
623 user commands need to pick up the selected frame before proceeding.
624
625 This is important. GDB is trying to stamp out the hack:
626
6e7f8b9c
AC
627 saved_frame = deprecated_selected_frame;
628 deprecated_selected_frame = ...;
abc0af47 629 hack_using_global_selected_frame ();
6e7f8b9c 630 deprecated_selected_frame = saved_frame;
abc0af47
AC
631
632 Take care! */
633
6e7f8b9c 634extern struct frame_info *deprecated_selected_frame;
abc0af47
AC
635
636
18ea5ba4 637/* Create a frame using the specified BASE and PC. */
abc0af47 638
18ea5ba4 639extern struct frame_info *create_new_frame (CORE_ADDR base, CORE_ADDR pc);
abc0af47 640
0394eb2a 641
2c517d0e
AC
642/* Create/access the frame's `extra info'. The extra info is used by
643 older code to store information such as the analyzed prologue. The
644 zalloc() should only be called by the INIT_EXTRA_INFO method. */
0394eb2a 645
2c517d0e
AC
646extern struct frame_extra_info *frame_extra_info_zalloc (struct frame_info *fi,
647 long size);
0394eb2a
AC
648extern struct frame_extra_info *get_frame_extra_info (struct frame_info *fi);
649
6baff1d2
AC
650/* Create/access the frame's `saved_regs'. The saved regs are used by
651 older code to store the address of each register (except for
652 SP_REGNUM where the value of the register in the previous frame is
653 stored). */
654extern CORE_ADDR *frame_saved_regs_zalloc (struct frame_info *);
655extern CORE_ADDR *get_frame_saved_regs (struct frame_info *);
656
b87efeee
AC
657/* FIXME: cagney/2002-12-06: Has the PC in the current frame changed?
658 "infrun.c", Thanks to DECR_PC_AFTER_BREAK, can change the PC after
659 the initial frame create. This puts things back in sync. */
2f107107
AC
660extern void deprecated_update_frame_pc_hack (struct frame_info *frame,
661 CORE_ADDR pc);
662
663/* FIXME: cagney/2002-12-18: Has the frame's base changed? Or to be
664 more exact, whas that initial guess at the frame's base as returned
665 by read_fp() wrong. If it was, fix it. This shouldn't be
666 necessary since the code should be getting the frame's base correct
667 from the outset. */
668extern void deprecated_update_frame_base_hack (struct frame_info *frame,
669 CORE_ADDR base);
b87efeee 670
c8b8a898
AC
671/* FIXME: cagney/2003-01-04: Explicitly set the frame's saved_regs
672 and/or extra_info. Target code is allocating a fake frame and than
673 initializing that to get around the problem of, when creating the
674 inner most frame, there is no where to cache information such as
675 the prologue analysis. This is fixed by the new unwind mechanism -
676 even the inner most frame has somewhere to store things like the
677 prolog analysis (or at least will once the frame overhaul is
678 finished). */
679extern void deprecated_set_frame_saved_regs_hack (struct frame_info *frame,
680 CORE_ADDR *saved_regs);
681extern void deprecated_set_frame_extra_info_hack (struct frame_info *frame,
682 struct frame_extra_info *extra_info);
683
684/* FIXME: cagney/2003-01-04: Allocate a frame from the heap (rather
685 than the frame obstack). Targets do this as a way of saving the
686 prologue analysis from the inner most frame before that frame has
687 been created. By always creating a frame, this problem goes away. */
688extern struct frame_info *deprecated_frame_xmalloc (void);
689
f6c609c4
AC
690/* FIXME: cagney/2003-01-05: Allocate a frame, along with the
691 saved_regs and extra_info. Set up cleanups for all three. Same as
692 for deprecated_frame_xmalloc, targets are calling this when
693 creating a scratch `struct frame_info'. The frame overhaul makes
694 this unnecessary since all frame queries are parameterized with a
695 common cache parameter and a frame. */
696extern struct frame_info *deprecated_frame_xmalloc_with_cleanup (long sizeof_saved_regs,
697 long sizeof_extra_info);
698
483d36b2
AC
699/* FIXME: cagney/2003-01-07: These are just nasty. Code shouldn't be
700 doing this. I suspect it dates back to the days when every field
701 of an allocated structure was explicitly initialized. */
702extern void deprecated_set_frame_next_hack (struct frame_info *fi,
703 struct frame_info *next);
704extern void deprecated_set_frame_prev_hack (struct frame_info *fi,
705 struct frame_info *prev);
706
2d75187b
AC
707/* FIXME: cagney/2003-01-07: Instead of the dwarf2cfi having its own
708 dedicated `struct frame_info . context' field, the code should use
709 the per frame `unwind_cache' that is passed to the
710 frame_pc_unwind(), frame_register_unwind() and frame_id_unwind()
711 methods.
712
713 See "dummy-frame.c" for an example of how a cfi-frame object can be
714 implemented using this. */
715extern struct context *deprecated_get_frame_context (struct frame_info *fi);
716extern void deprecated_set_frame_context (struct frame_info *fi,
717 struct context *context);
718
c906108c 719#endif /* !defined (FRAME_H) */
This page took 0.554757 seconds and 4 git commands to generate.