Brian Wainscott <[EMAIL PROTECTED]> writes:
>
> tom fogal wrote:
>
> > Brian Wainscott <[EMAIL PROTECTED]> writes:
> >
> >> But I'm still seeing LOTS of these which I didn't see in earlier
> >> versions of valgrind (circa. 2 years ago, I don't remember the
> >> version number).
> >
> > Why is this an issue? This code is \emph{wrong}. It doesn't matter
> > that valgrind didn't notice until it was passed into printf. If
> > earlier versions of valgrind did not report this error, then earlier
> > versions of valgrind are buggy.
>
> This code is wrong, of course. But I've got code where I've seen so many
> of these reports it is pretty much useless to me.
Okay. I misunderstood the purpose of your mail. You're concerned that
you've got a program with so many errors, but you're 99% sure that most
of the ones memcheck reports aren't related to the one critical bug
you're currently searching for. A needle in a haystack of bugs.
I suppose the cop-out response is `fix all your bugs!', but I
understand debugging time is scarce at best.
So try a suppression. Quick guess:
{
BW:quietness
Memcheck:Value8
fun:printf
}
Beware, I've not even tested if VG parses that.
More info:
http://valgrind.org/docs/manual/manual-core.html#manual-core.suppress
(or try --gen-suppressions=yes).
I'm sure you know this, but I would be remiss if I did not explicitly
note that, of course, if the `larger' error you search for is only
visible in a printf, you won't see it with such a suppression.
Good luck,
-tom
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
