Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
howto:panel_plugin_debug [2009/01/14 12:53] – 88.172.125.130howto:panel_plugin_debug [2009/01/14 13:36] – 88.172.125.130
Line 28: Line 28:
 {{wiki:information.png}} It'll be really slow as wrapped in valgrind, but you'll be able to hunt memory leaks. {{wiki:information.png}} It'll be really slow as wrapped in valgrind, but you'll be able to hunt memory leaks.
  
-==== More useful call to Valgrind ====+=== More useful call to Valgrind ===
  
   G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --tool=memcheck --leak-check=full \   G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --tool=memcheck --leak-check=full \
Line 48: Line 48:
   gdb -ex r -ex bt -ex q --args /usr/local/libexec/xfce4/panel-plugins/clipman $@ \   gdb -ex r -ex bt -ex q --args /usr/local/libexec/xfce4/panel-plugins/clipman $@ \
   > $HOME/clipman-gdb.log 2>&1   > $HOME/clipman-gdb.log 2>&1
 +
 +=== Using GDB on running instances ===
  
 If you want an interactive debug session with GDB, you can simply find the process id of the plugin by running If you want an interactive debug session with GDB, you can simply find the process id of the plugin by running
Line 55: Line 57:
   (gdb) continue   (gdb) continue
  
-which will find the PID of clipman, and debug it using the debug symbols in /usr/local/libexec/xfce4/panel-plugins/clipman. For this to work, clipman must already be running. You can also attach GDB to a processfrom the GDB prompt by using the attach command:+which will find the PID of clipman, and debug it using the debug symbols in /usr/local/libexec/xfce4/panel-plugins/clipman. For this to work, clipman must already be running. You can also attach GDB to a process from the GDB prompt by using the attach command:
  
   (gdb) attach $PID   (gdb) attach $PID