Re: memory leak reported many times, but only one instance should be possible

On 16-01-23 22:02, Gordon Messmer wrote:

> Can anyone suggest why valgrind prints so many loss records for this 
> particular leak?  Links for the two functions that I mentioned follow, 
> along with one of the loss records printed by valgrind.


In my experience the most likely reason that you are getting a large 
number of leaks reported by Valgrind is that there is a large number of 
leaks.

You need more stack depth to see all of the stack.

Otherwise you can use gdb and put a breakpoint on malloc to confirm the 
allocations.

A+
Paul


_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users