|
From: Tom H. <th...@cy...> - 2003-08-29 19:50:47
|
In message <608...@pd...>
Brian Mosher <bm...@di...> wrote:
> It sounds like there is additional output that I should be seeing. Am I
> missing something? When you say that there is a second half to the error
> report -- Is that a summary group at the bottom of the report, or will the
> additional info appear along with the error statement in the body of the
> output?
My mistake - you only get the second part of the report if the
uninitialised value is in memory. If it's in a register then you
don't as there isn't much to say.
Your best bet in that case is to inspect the code at the failing
location and see if there is an obvious cause, and if not then to
try inserting some assertions using the valgrind macros to try and
work out what is uninitialised - assertions like this will do it:
assert( !VALGRIND_CHECK_READABLE( &variable, sizeof( variable ) ) );
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|