Uh, I wasn't implying that. Only that I have a fair amount of experience as a Unix software developer, and I had trouble following the instructions on the Wiki page to get this debug information. There are two things that have confused me:
* The fact that the -dbgsym packages actually only provide extra debug information in files in /usr/lib/debug, and not whole new executables with debug information. I wasn't aware that this was possible, so when I saw it didn't modify the existing executables, and that /usr/bin/file said that the new /usr/lib/debug files were in fact ELF executables, the natural thing for me to do was to try to run them, which fails miserably. I was just asking for a hint to be placed on the wiki page to that effect, to prevent further confusion. * The fact that this is a gnome-panel applet, and in fact the way to debug it is very non-obvious. The Ubuntu Valgrind wiki page contains nothing about how to do this. I finally found something here: http://www.davyd.id.au/articles/debugging-gnome-applets.shtml , but I think in general most bug reporters are not going to go to that much effort to find this out. Anyway, it looks like the leak is possibly in libgtop or how it is called from the system applet. I'll post full valgrind dumps in a bit. -- multiload-applet-2 leaks memory https://bugs.launchpad.net/bugs/307472 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
