|
From: Paul P. <ppl...@gm...> - 2006-01-19 05:01:46
|
On 19 Jan 2006 04:29:04 +0000, Bryan Henderson <br...@gi...> wr= ote: > My personal strategy is to look at every "Invalid read of size 4" and if > it just runs off the end of an odd-sized block, I write a suppression for > it. I don't try to determine if there's a real problem; I just presume > there isn't. If the bad read comes from libc, your strategy is possibly ok, though you may miss bugs where you pass a "too small" buffer into libc. If it comes from your own code, it is almost certainly a bug in your code (unless you also perform "ultra-optimizations", and you should fix it instead of suppressing. > So why can't Valgrind do that for me? Why not run with --tool=3Dnone ? That way you wouldn't get any reports at all. Cheers, |