|
From: Ajay K. <kal...@gm...> - 2010-05-14 06:28:08
|
Hi Using valgrind is it possible to detect memory leaks without killing the process i.e as they happen. I see memory errors being reported as it happens but not leaks Ajay |
|
From: Alexander P. <gl...@go...> - 2010-05-14 07:18:41
|
Generally you can't tell that a memory allocation is a leak until the process stops. In C/C++ the program can still access a memory region even if there are no pointers to it, so an allocated memory chunk can be freed at any time. HTH, Alex |
|
From: Julian S. <js...@ac...> - 2010-05-14 08:03:11
|
On Friday 14 May 2010, Ajay Kalambur wrote: > Hi > Using valgrind is it possible to detect memory leaks without killing the > process i.e as they happen. It depends what you mean. It can't tell you the place where the last pointer to a block was overwritten. But you can ask for a leak check at any time, see VALGRIND_DO_LEAK_CHECK at http://www.valgrind.org/docs/manual/mc-manual.html#mc-manual.clientreqs J |