|
From: Nicholas N. <nj...@cs...> - 2005-10-17 19:24:06
|
On Mon, 17 Oct 2005, Tom Hughes wrote: >> There is one issue though: It looks like Valgrind reports partial loads >> as errors by default. I think this shouldn't be the default behavior. > > Actually valgrind doesn't report any loads as errors - it only > reports an error when you use an undefined value in a way that > would effect the result of the program. In other words when a > conditional jump depends on it or you use it as a pointer and > read or write through that pointer. > > It tracks definedness at bit level, so a partial load will mark > some bits as defined and leaves others alone. If you then later > use one of the undefined bits it will complain. > > There are edge cases where it thinks a bit is used when it isn't > really but they are rare. > > I think you need to explain what you mean more fully. I think he's referring to the --partial-loads-ok option, but it's set to true by default (at least, that's what "valgrind -h" says). Nick |