|
From: Paul P. <ppl...@gm...> - 2005-01-13 03:50:35
|
On Wed, 12 Jan 2005 15:29:40 -0500, Chris Shoemaker <c.s...@co...> wrote: > Is there a way to make valgrind report the _read_ of an uninitialized > value instead of waiting until a conditional jump depends on it? This is what Chaperon (part of commercial Insure++ product from Parasoft) does. Unfortunately, this tends to produce a lot of "noise": some versions of gcc emit code that copies around uninitialized values (the copies are never used either). With VG strategy you have a real bug but have trouble finding the root cause. With Chaperon, you (sometimes) have a lot of "false positives". Either way, you loose :-( |