|
From: Brian M. <bm...@di...> - 2003-08-29 20:48:31
|
> > 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 ) ) ); > Ah, it must be in a register -- of course, I should have thought of that. Thanks for the tip about the macro. I'll give it a try. Thanks again, --Brian |