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

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

On Wed, 2003-05-14 at 10:45, Bastien Chevreux wrote:
> On Wednesday 14 May 2003 11:37, Crispin Flowerday wrote:
> > While attempting to locate all the memory in a program that wasn't
> > freed, I came across an odd behaviour.
> > [...]
> > I get only 2 unreachable blocks, but both with the same stacktrace:
> 
> Does using the --num-callers option help?

No, I just get a longer stacktrace :)

Crispin