Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
howto:panel_plugin_debug [2007/12/09 20:28] – reformat a bit (useless I know, I'm borred) 88.172.125.130 | howto:panel_plugin_debug [2012/11/26 12:59] (current) – removed nick | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Panel Plugin Debugging ====== | ||
- | |||
- | An easy way to debug an external panel-plugin with Valgrind : | ||
- | |||
- | * In / | ||
- | * Create an executable shellscript named foo-plugin in the same place, containing : | ||
- | |||
- | #!/bin/sh | ||
- | valgrind --log-file=/ | ||
- | |||
- | * Add the plugin to the panel as usual | ||
- | Note. It'll be really slow as wrapped in valgrind, but you'll be able to hunt memory leaks using tail -f / | ||
- | |||
- | |||
- | ===== Alternative way ===== | ||
- | Edit your .desktop file of the plugin (for most easy results, directly in the source directory) and append .valgrind to the xfce-exec line. Then create a file like described above, but named xfce4-my-plugin.valgrind in the same location. It will never ever be overwritten by any of your subsequent installations, | ||
- | |||
- | Pay attention to edit the xfce-exec line before checking into subversion or making a release. | ||
- | |||
- | ===== More senseful call to Valgrind ===== | ||
- | |||
- | '' | ||