Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2012-02-05 15:13:36 →
Size: 840
Editor: Wilmer
Comment:
← Revision 4 as of 2012-03-22 15:55:01 → ⇥
Size: 847
Editor: dsl4E5C0633
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
gdb ./bitlbee -v -n -D 2>&1 | tee /tmp/gdb.log gdb --args ./bitlbee -v -n -D 2>&1 | tee /tmp/gdb.log

How to get backtrace (on Linux)?

The backtrace is useful when the application crashes or freezes. You might use the following steps:

1. Rebuild BitlBee with --debug=1 (if you're using the Debian packages from http://code.bitlbee.org/debian/ you don't need to do this)

2. Start the debugger with the binary and log the output: 

gdb --args ./bitlbee -v -n -D 2>&1 | tee /tmp/gdb.log

3. Inside the debugger, start the application: 

run

4. Do the steps to reproduce the application crash or freeze. If the freeze is the case, you need to press CTRL-C in gdb to get the gdb commandline back.

5. Produce the backtrace: 

bt

6. Quit the debugger 

quit

7. Attach the whole gdb.log to the bug report. Remember to include the exact BitlBee version used to create your backtrace.

BitlBee Wiki: DebuggingCrashes (last edited 2018-02-06 17:11:06 by 2800:810:46b:747:76d4:35ff:feeb:fa02)