Lines Matching full:prologue
297 3.1 Prologue Analysis
312 called "prologue analysis" to find frame sizes and saved registers. A
313 prologue analyzer disassembles the function's machine code starting
318 Prologue analysis predates the GNU toolchain's support for CFI; at one
319 time, prologue analysis was the only mechanism GDB used for stack
326 write a prologue analyzer for GDB that would accurately understand all
329 about the semantics of the prologue instructions themselves; in
331 prologue analyzers working as GCC (and the instruction sets themselves)
334 To try to address this problem, the code in `prologue-value.h' and
335 `prologue-value.c' provides a general framework for writing prologue
337 we analyze a prologue using the prologue-value framework, we're really
385 Using this framework, a prologue analyzer is simply an interpreter
397 prologue has done something too complex for us to track, and we
408 This does take some work. But prologue analyzers aren't
409 quick-and-simple pattern patching to recognize a few fixed prologue
411 function calls, prologue analysis accounts for a substantial portion of
431 The file `prologue-value.h' contains detailed comments explaining
3417 * Prologue Caches::
3549 File: gdbint.info, Node: Frame Handling Terminology, Next: Prologue Caches, Prev: All About Stack Frames, Up: Frame Interpretation
3605 File: gdbint.info, Node: Prologue Caches, Next: Functions and Variable to Analyze Frames, Prev: Frame Handling Terminology, Up: Frame Interpretation
3607 11.7.3 Prologue Caches
3614 function "prologue".
3618 NEXT frame as their first argument, receive a pointer to a "prologue
3632 frame, the prologue sniffer for THIS frame will be `NULL'. The sniffer
3633 will analyze the frame, allocate a prologue cache structure and
3635 this prologue cache, so the data can be returned with no additional
3639 File: gdbint.info, Node: Functions and Variable to Analyze Frames, Next: Functions to Access Frame Data, Prev: Prologue Caches, Up: Frame Interpretation
3650 The prologue of a function is the code at the beginning of the
3653 after the prologue.
3655 This function skips past the prologue of a function if the program
3656 counter, PC, is within the prologue of a function. The result is
3657 the program counter immediately after the prologue. With modern
3702 functions without prologue or epilogue or by exception handlers
3845 prologue cache for this frame (*note Prologue Caches: Prologue
8212 * function prologue: Prologue Caches. (line 6)
8530 * prologue analysis: Algorithms. (line 14)
8531 * prologue cache: Prologue Caches. (line 12)
8532 * prologue of a function: Prologue Caches. (line 6)
8533 * prologue-value.c: Algorithms. (line 48)
8812 Node: Prologue Caches151860
