https://bugzilla.novell.com/show_bug.cgi?id=811435 https://bugzilla.novell.com/show_bug.cgi?id=811435#c8 --- Comment #8 from Vincent Untz <vuntz@suse.com> 2013-05-24 09:07:03 UTC --- Sorry for the late reply; this got lost in my "I left for vacation" mails ;-) (In reply to comment #7)
This is using the alternate approach. It really hurt my system, badly when I used --leak-check=full, and seems to lack the desired output?
Indeed, it lacks what we want. Not sure why :/
How do I have to close/kill gnome-panel in this case? A simple logout does not seem to do it? Nor does killing /usr/lib64/valgrind/memcheck-amd64-linux?
You should be able to issue a "gnome-panel --replace" to start a new instance of the panel. But logging out certainly should be enough to have it stop. Maybe there's some race because valgrind makes it so slow, and it doesn't catch the signal? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.