FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* gdb.texinfo (Backtraces): Document "set backtrace-below-main".

Browse source 
* gdbint.texinfo (FRAME_CHAIN_VALID): Update documentation.
This commit is contained in:
Daniel Jacobowitz 2003-01-05 01:38:41 +00:00
parent f6b33856d3
commit 95f90d2595
3 changed files with 31 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

5
gdb/doc/ChangeLog
View file

@ -1,3 +1,8 @@
2003-01-04 Daniel Jacobowitz <drow@mvista.com>
* gdb.texinfo (Backtraces): Document "set backtrace-below-main".
* gdbint.texinfo (FRAME_CHAIN_VALID): Update documentation.
2003-01-04 Daniel Jacobowitz <drow@mvista.com> 2003-01-04 Daniel Jacobowitz <drow@mvista.com>
* gdb.texinfo (Controlling GDB): Add ABI section. Document * gdb.texinfo (Controlling GDB): Add ABI section. Document

20
gdb/doc/gdb.texinfo
View file

@ -3857,6 +3857,26 @@ The display for frame zero does not begin with a program counter
value, indicating that your program has stopped at the beginning of the value, indicating that your program has stopped at the beginning of the
code for line @code{993} of @code{builtin.c}. code for line @code{993} of @code{builtin.c}.
Most programs have a standard entry point---a place where system libraries
and startup code transition into user code. For C this is @code{main}.
When @value{GDBN} finds the entry function in a backtrace it will terminate
the backtrace, to avoid tracing into highly system-specific (and generally
uninteresting) code. If you need to examine the startup code, then you can
change this behavior.
@table @code
@item set backtrace-below-main off
Backtraces will stop when they encounter the user entry point. This is the
default.
@item set backtrace-below-main
@itemx set backtrace-below-main on
Backtraces will continue past the user entry point to the top of the stack.
@item show backtrace-below-main
Display the current backtrace policy.
@end table
@node Selection @node Selection
@section Selecting a frame @section Selecting a frame

26
gdb/doc/gdbint.texinfo
View file

@ -3277,26 +3277,12 @@ Given @var{frame}, return a pointer to the calling frame.
@item FRAME_CHAIN_VALID(@var{chain}, @var{thisframe}) @item FRAME_CHAIN_VALID(@var{chain}, @var{thisframe})
@findex FRAME_CHAIN_VALID @findex FRAME_CHAIN_VALID
Define this to be an expression that returns zero if the given frame is Define this to be an expression that returns zero if the given frame is an
an outermost frame, with no caller, and nonzero otherwise. Several outermost frame, with no caller, and nonzero otherwise. Most normal
common definitions are available: situations can be handled without defining this macro, including @code{NULL}
chain pointers, dummy frames, and frames whose PC values are inside the
@itemize @bullet startup file (e.g.@: @file{crt0.o}), inside @code{main}, or inside
@item @code{_start}.
@code{file_frame_chain_valid} is nonzero if the chain pointer is nonzero
and given frame's PC is not inside the startup file (such as
@file{crt0.o}).
@item
@code{func_frame_chain_valid} is nonzero if the chain
pointer is nonzero and the given frame's PC is not in @code{main} or a
known entry point function (such as @code{_start}).
@item
@code{generic_file_frame_chain_valid} and
@code{generic_func_frame_chain_valid} are equivalent implementations for
targets using generic dummy frames.
@end itemize
@item FRAME_INIT_SAVED_REGS(@var{frame}) @item FRAME_INIT_SAVED_REGS(@var{frame})
@findex FRAME_INIT_SAVED_REGS @findex FRAME_INIT_SAVED_REGS