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

docs/debugging: use logs.i3wm.org

This commit is contained in:
Michael Stapelberg 2015-02-04 19:54:07 +01:00
parent 72b3c9f4c9
commit 663235c714
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/debugging
View File

@ -72,15 +72,17 @@ i3-msg 'debuglog on; shmlog on; reload'
No matter whether i3 misbehaved in some way without crashing or whether it just No matter whether i3 misbehaved in some way without crashing or whether it just
crashed, the logfile provides all information necessary to debug the problem. crashed, the logfile provides all information necessary to debug the problem.
To save a compressed version of the logfile (suitable for attaching it to a To upload a compressed version of the logfile (for a bugreport), use:
bugreport), use: ------------------------------------------------------------------------------
-------------------------------------------------------------------- DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- http://logs.i3wm.org
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.
After running it, you will get a URL to the logfile. Please include that URL in
your bug report.
== On crashes: Obtaining a backtrace == On crashes: Obtaining a backtrace
When i3 crashes, it will display a dialog stating “i3 just crashed”, offering When i3 crashes, it will display a dialog stating “i3 just crashed”, offering