From 95f90d2595724210a3f27456baeb6eed02ece2bc Mon Sep 17 00:00:00 2001 From: Daniel Jacobowitz Date: Sun, 5 Jan 2003 01:38:41 +0000 Subject: * gdb.texinfo (Backtraces): Document "set backtrace-below-main". * gdbint.texinfo (FRAME_CHAIN_VALID): Update documentation. --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdb.texinfo | 20 ++++++++++++++++++++ gdb/doc/gdbint.texinfo | 26 ++++++-------------------- 3 files changed, 31 insertions(+), 20 deletions(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index c7e26c7..a24ee2f 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,5 +1,10 @@ 2003-01-04 Daniel Jacobowitz + * gdb.texinfo (Backtraces): Document "set backtrace-below-main". + * gdbint.texinfo (FRAME_CHAIN_VALID): Update documentation. + +2003-01-04 Daniel Jacobowitz + * gdb.texinfo (Controlling GDB): Add ABI section. Document "set coerce-float-to-double". * gdbint.texinfo (COERCE_FLOAT_TO_DOUBLE): Remove documentation. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index af42b00..0f7ed9f 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -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 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 @section Selecting a frame diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index 9ce6ecb..78de357 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -3277,26 +3277,12 @@ Given @var{frame}, return a pointer to the calling frame. @item FRAME_CHAIN_VALID(@var{chain}, @var{thisframe}) @findex FRAME_CHAIN_VALID -Define this to be an expression that returns zero if the given frame is -an outermost frame, with no caller, and nonzero otherwise. Several -common definitions are available: - -@itemize @bullet -@item -@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 +Define this to be an expression that returns zero if the given frame is an +outermost frame, with no caller, and nonzero otherwise. Most normal +situations can be handled without defining this macro, including @code{NULL} +chain pointers, dummy frames, and frames whose PC values are inside the +startup file (e.g.@: @file{crt0.o}), inside @code{main}, or inside +@code{_start}. @item FRAME_INIT_SAVED_REGS(@var{frame}) @findex FRAME_INIT_SAVED_REGS -- cgit v1.1