|
From: Nicholas N. <nj...@cs...> - 2005-03-04 21:09:15
|
On Fri, 4 Mar 2005, Olly Betts wrote: > This is your problem then. For floating point values, valgrind issues > an error when reading an uninitialised value from memory (for integer > values, the error isn't issued until the uninitialised value can affect > control flow or is passed to a system call, because the assembler code > compilers generate often copies around uninitialised integer values - > for example when copying a structure including uninitialised padding > bytes). > > You should be able to generate a suppression for this case if you're > happy it's safe to ignore this. Nb: This inaccuracy with FP values should be removed in Valgrind releases sometime later this year (but definitely not the next release). N |