Changes between Version 30 and Version 31 of Debugging

Timestamp:

12/12/13 08:35:10 (7 years ago)

Author:

Antoine Martin

Comment:

--

Debugging

@@ -109 +109 @@
 == GDB ==
 When dealing with crashes ("core dumped"), the best way to debug is to fire gdb.
-=== Getting a Backtrace ===
+=== Attaching to an existing xpra process ==
+Find the pid of the xpra process:
 {{{
-xpra start ...
-# or xpra attach ...
 ps -ef | grep xpra
+}}}
+Then:
+{{{
 gdb python $PID_OF_XPRA_PROCESS_TO_DEBUG
 # wait for it to load all the debug symbols
 (gdb) continue
 }}}
+
+=== Starting xpra in gdb ===
+{{{
+gdb python $PID_OF_XPRA_PROCESS_TO_DEBUG
+run /usr/bin/xpra start ...
+}}}
+
+=== Getting the backtrace ===
 Then once you get a crash, gdb should show you its prompt again and you can extract the python stacktrace with {{{py-bt}}} and the full stacktrace with {{{bt}}}. Having both is useful.
 Note: installing the required "debug" symbol packages for your distribution is out of scope, please refer to your vendor's package manager for details (ie: [http://wiki.debian.org/HowToGetABacktrace debian] and [http://yum.baseurl.org/wiki/YumUtils/DebugInfoInstall yum debuginfo-install]).