Re: [Valgrind-users] Seemingly wrong reachable-memory reporting

[Crispin F. <cr...@th...>]

> Ah;  by default, the leak checker only compares the first two names in the
> stack trace for the purposes of merging leak record.  Try
> --leak-resolution=med.
> 
> (2.96 gave two leak records because it didn't have the "operator new[]"
> line in the stack trace, so dostuff/dostuff1 made it into the first two
> names.)

Ahh, that explains it. Perhaps the leak-resolution should default to med
or high as the output was extremely confusing (much worse when you have
a large application and valgrind has merged 10 blocks into a single
stacktrace).

Cheers

Crispin