Re: [Valgrind-users] 2.1.0 Syscall error reporting

[Steve G <lin...@ya...>]

>It can get pretty noisy.  There's quite a few programs which 
>do lots of indiscriminate closing of fds.

I'd say give 'em the output. If its noisy, it should be a clue
that something needs fixing. They should be able to generate a
suppression for it if its too painful.

The issue that I'm really thinking should be a avoided is when
you are working on something that has a race condition and its
hard to trigger the error. The way it currently is, you would
have to try to reproduce the race just to find out where the
problem was coming from.

I think its more consistent if warnings were printed by default
and suppressions reduce the noise. Memory problems are printed by
default, so why not syscall problems? (I think version 1.9.6
printed stack traces for syscall problems.)

-Steve Grubb

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/