tags 282210 moreinfo unreproducible kthxbye On Sat, Nov 20, 2004 at 02:28:10PM +0100, Jens Thiele (karme) wrote: > Package: valgrind > Version: 1:2.2.0-3 > Severity: normal > > I am using valgrind for automatic software testing > and I am missing an easy way to distinguish between warnings and errors > > for example: > valgrind -q --leak-check=yes still produces output like this: > (though the man-page says -q should only print errors) > > ==13865== warning: Valgrind's pthread_getschedparam is incomplete > ==13865== your program may misbehave as a result > ==13865== warning: Valgrind's pthread_setschedparam does nothing > ==13865== (scheduling not changeable) > ==13865== your program may misbehave as a result > ==13865== warning: Valgrind's pthread_cond_destroy is incomplete > ==13865== (it doesn't check if the cond is waited on) > ==13865== your program may misbehave as a result > ==13865== warning: Valgrind's pthread_cond_destroy is incomplete > ==13865== (it doesn't check if the cond is waited on) > ==13865== your program may misbehave as a result > ==13865== warning: Valgrind's pthread_cond_destroy is incomplete > ==13865== (it doesn't check if the cond is waited on) > ==13865== your program may misbehave as a result
I cannot reproduce this with valgrind from unstable. Does this still happen to
you? If so, could you please provide a little snippet of code to reproduce it?
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
