RE: [Valgrind-users] Question about uninitialized references

[Vincent Penquerc'h <Vin...@ar...>]

> Just a curious question.  What is valgrind's test for "dealing"
> with uninitialized data?  It appears reading it moving it around 
> is OK, but using it to perform "a computation" is an error?  But 
> what is "a computation" in this context?

Whatever would make the behavior of the program undefined, I'd
say. This is covered in the docs, along with a note that moving
uninitialized stuff is often done. Like, say, in the following:

typedef struct {
  int is_used;
  int data;
} foo;

foo f,g;
f.is_used = 0;
g=f;


-- 
Vincent Penquerc'h