|Debugging with GDB||www.imodulo.com · 2003-04-05|
|[ Software | Documentation | Contact ]|
A backtrace is a summary of how your program got where it is. It shows one line per frame, for many frames, starting with the currently executing frame (frame zero), followed by its caller (frame one), and on up the stack.
Print a backtrace of the entire stack: one line per frame for all frames in the stack.
You can stop the backtrace at any time by typing the system interrupt character, normally C-c.
Similar, but print only the innermost n frames.
Similar, but print only the outermost n frames.
info stack (abbreviated
info s) are additional aliases for
Each line in the backtrace shows the frame number and the function name. The program counter value is also shown--unless you use
set print address off. The backtrace also shows the source file name and line number, as well as the arguments to the function. The program counter value is omitted if it is at the beginning of the code for that line number.
Here is an example of a backtrace. It was made with the command
bt 3, so it shows the innermost three frames.
#0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8) at builtin.c:993 #1 0x6e38 in expand_macro (sym=0x2b600) at macro.c:242 #2 0x6840 in expand_token (obs=0x0, t=177664, td=0xf7fffb08) at macro.c:71 (More stack frames follow...)
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
|© Free Software Foundation, Inc.|