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. You can stop the backtrace at
any time by typing the system interrupt character, normally
Ctrl-c. bt full -n bt no-filters -n bt no-filters full bt no-
filters fulln bt no-filters full -n info stack (abbreviated are
additional aliases for In a multi-threaded program, gdb by
default shows the backtrace only for the current thread. To
display the backtrace for several or all of the threads, use the
command (see thread apply). For example, if you type thread
apply all backtrace, gdb will display the backtrace for all the
threads; this is handy when you debug a core dump of a Each line
in the backtrace shows the frame number and the function name.
The program counter value is also shown—unless you use print
address off. The backtrace also shows the source file name and
line number, as well as th