nixo
/
gri3-wm
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs/debugging: merge the debug symbols/backtrace section 

We rarely have crashes, almost always we just need logs.
This commit is contained in:
Michael Stapelberg 2014-01-04 12:04:43 +01:00
parent 2c06dc0a1f
commit 92a50db29e
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/debugging
View File

@ -81,7 +81,10 @@ DISPLAY=:0 i3-dump-log | bzip2 -c > /tmp/i3.log.bz2
This command does not depend on i3 (it also works while i3 displays This command does not depend on i3 (it also works while i3 displays
the crash dialog), but it requires a working X11 connection. the crash dialog), but it requires a working X11 connection.
== Compiling with debug symbols == On crashes: Obtaining a backtrace
When i3 crashes, it will display a dialog stating “i3 just crashed”, offering
you to save a backtrace to a text file.
To actually get useful backtraces, you should make sure that your version of i3 To actually get useful backtraces, you should make sure that your version of i3
is compiled with debug symbols: is compiled with debug symbols:
@ -97,8 +100,6 @@ which is stripped, please check whether your distribution provides debug
symbols (package +i3-wm-dbg+ on Debian for example) or if you can turn off symbols (package +i3-wm-dbg+ on Debian for example) or if you can turn off
stripping. If nothing helps, please build i3 from source. stripping. If nothing helps, please build i3 from source.
== Obtaining a backtrace
Once you have made sure that your i3 is compiled with debug symbols and the C Once you have made sure that your i3 is compiled with debug symbols and the C
debugger +gdb+ is installed on your machine, you can let i3 generate a debugger +gdb+ is installed on your machine, you can let i3 generate a
backtrace in the crash dialog. backtrace in the crash dialog.