|
From: Olly B. <ol...@su...> - 2005-03-04 20:20:55
|
On 2005-03-04, Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca> wrote:
> It's normal that in the first
> few iterations, uninitialized values are moved around in best_dist, but
> in the end, they are guarantied to be all gone and nothing ever depends
> on these uninitialized values.
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.
Cheers,
Olly
|