Re: [Valgrind-users] Valgrind does leak detection across fork()

[Nicholas N. <nj...@ca...>]

On Sun, 30 Nov 2003, Avery Pennarun wrote:

> > I disagree.  There is an important difference between true space leaks,
> > and memory that you just didn't bother to free ("reachable").  Even
> > programs that call _exit() shouldn't have true space leaks.  And a few
> > lines of output showing memory that was reachable doesn't seem like a big
> > inconvenience.  In this example, Memcheck distinguishes the two cases
> > exactly how I would want and expect it to.
>
> In this particular case, I want to suppress scary-looking output (ie.
> anything from valgrind) because it happens in the middle of my unit tests,
> and scary-looking output from my unit tests should constitute a bug, not a
> bonus valgrind feature :)

Are you using -q?  In that case, I think you do not want Valgrind to not
leak-check fork() children, but to just be quieter, and only print a
message if there is a genuine leak.  Is that right?

N