Xfce Wiki

Sub domains
 

Differences

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

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
xfce:xfce4-panel:debugging [2012/01/18 14:32] – created nickxfce:xfce4-panel:debugging [2014/03/14 10:54] – [Debugging] nick
Line 3: Line 3:
 The Xfce Panel has a number of tools to create good [[https://bugzilla.xfce.org|bug reports]]. It can also give some valuable insight for users how the panel works, in case you have problems. The Xfce Panel has a number of tools to create good [[https://bugzilla.xfce.org|bug reports]]. It can also give some valuable insight for users how the panel works, in case you have problems.
  
 +=== See Also ===
 +
 +[[:contribute:bugs:start]]\\
 +Information about reporting bugs and generating backtraces.
 +
 +[[:xfce:building]]\\
 +How to compile Xfce from source to provide better debug information.
 ===== Debug Logs ===== ===== Debug Logs =====
  
Line 18: Line 25:
 ==== GDB ==== ==== GDB ====
  
-If you start the panel with ''PANEL_DEBUG=gdb'' and [[http://www.gnu.org/software/gdb/|gdb]] is installed on your computer, all external plugins.+If you start the panel with ''PANEL_DEBUG=gdb'' and [[http://www.gnu.org/software/gdb/|gdb]] is installed on your computer, all external plugins will be started in gdb. The output of //gdb// is written to ''/tmp/<stamp>_gdb_<plugin-name>_<plugin-id>.log''. If the plugin segfaults, it will automatically create a //backtrace full// and dump //info registers//.
  
-==== Valgrind ====+This does not mean the output contains valuable information. For good backtraces it is still recommended to create a debug-build of the plugin.
  
 +==== Valgrind ====
  
 +To detect memory leaks and corruptions, it is also possible to run plugins in [[http://valgrind.org/|valgrind]]. For this start the panel with ''PANEL_DEBUG=valgrind''. Logs will be written to the same location as the //gdb// logs.