https://bugs.kde.org/show_bug.cgi?id=445627
Tom Hughes <t...@compton.nu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |NOT A BUG
CC| |t...@compton.nu
--- Comment #1 from Tom Hughes <t...@compton.nu> ---
This is a bug tracker - enquiries about how to use valgrind are better directed
to the users mailing list.
If the leak summary is printed immediately then the program you are running is
exiting immediately and you're not actually running your program under
valgrind.
Most likely you have run valgrind on a shell script or other launcher that then
launches the real program and you're not using --trace-children=yes so valgrind
exits when that initial launcher does and tells you about leaks in the
launcher. If you are using --trace-children=yes then valgrind will still be
tracing the launched program and will issue an additional report when that
exits.
--
You are receiving this mail because:
You are watching all bug changes.
