Backtrace

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2006-05-01 19:27:14 →
Size: 1130
Editor: ottawa-hs-64-26-167-206
Comment: Description
← Revision 3 as of 2006-05-01 21:08:51 → ⇥
Size: 1207
Editor: ottawa-hs-64-26-167-206
Comment: Remind people to install gdb.
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 1. Make sure the GNU Debugger is installed. {{{
apt-get install gdb
}}}

A backtrace shows a listing of which program functions are still active. Since functions are nested when they are called, the program must record where it left one function, to jump into an inner one. It does this on the stack, which we dump for the backtrace,

By getting a backtrace at the point of a bug, a developer may be able to isolate where that bug is, because it will narrow down to the function, or even the line, that caused the erroneous behaviour.

Generation

Please ensure you have packages with debug symbols installed. You can do this by following the instructions at DebuggingProgramCrash.

  1. Make sure the GNU Debugger is installed. 

    apt-get install gdb

  2. Start the program under control of gdb: 

    gdb <program>
(gdb) handle SIG33 pass nostop noprint
(gdb) run <arguments, if any>
  3. The program will start. Perform any actions necessary to reproduce the crash

  4. Retrieve a backtrace of the crash: 

    (gdb) thread apply all bt

  5. If the output gets very long, you might want to use: 

    (gdb) set logging file backtrace.txt
(gdb) set logging on
    beforehand.
  6. Include the complete output from GDB in your bug report.

Backtrace (last edited 2022-12-20 22:15:16 by sergiodj)