Bug 445627

Summary:	Query on Leak summary
Product:	[Developer tools] valgrind	Reporter:	amita dwivedi <amita1612>
Component:	memcheck	Assignee:	Julian Seward <jseward>
Status:	RESOLVED NOT A BUG
Severity:	major	CC:	tom
Priority:	NOR
Version First Reported In:	3.15 SVN
Target Milestone:	---
Platform:	Other
OS:	Other
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description amita dwivedi 2021-11-17 07:26:49 UTC

Can you please let us know how to check for memory leak or to print that output again when we need.
This is required when we do a 24 hour run on Valgrind and check memory leak after 24 hours.

Currently the leak summary gets printed at the very beginning of testing.

Comment 1 Tom Hughes 2021-11-17 08:34:58 UTC

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.