Re: [Valgrind-users] Using valgrind from a test suite

[Olly B. <ol...@su...>]

On Sat, Mar 29, 2003 at 10:19:18PM +0000, Nicholas Nethercote wrote:
> On Fri, 28 Mar 2003, Olly Betts wrote:
> 
> > > >   int VALGRIND_SILENT(int silent);
> > > >
> > > >     If silent is non-zero, suppress *all* output from valgrind.  Returns
> > > >     the setting prior to the call.
> 
> I think a command line option is more appropriate for this.  Currently
> -q turns off all normal output, but still prints errors.  Using -q -q
> could suppress everything.  Although this would be useless without using
> the following client requests, so maybe a client request is a good way to
> do it.

I did consider a command line option, but went for the client request
for that reason.

A third possibility I've just thought of is to use:

valgrind --logfile-fd=-1 /dev/null [program and args]

(Or redirect to a particular fd and direct that to /dev/null but then
that fd might be used by something - -1 is nice as it always works...)

If this is the preferred approach perhaps it should be documented that
"--logfile-fd=-1" will suppress messages to avoid worries that a future
valgrind might check the supplied fd is writable...

For my purposes, VALGRIND_SILENT certainly isn't vital.

> All in all, they're pretty minor changes, and I think it's a good thing to
> make it easier to incorporate Valgrind into regression testing.  So I'd be
> happy to add them, but only once I've done my core/skin reshuffle
> (assuming it is completed), which will take a little while.

Cool.

Cheers,
    Olly