|
From: Nicholas N. <nj...@ca...> - 2004-08-26 11:14:27
|
On Thu, 26 Aug 2004, Tom Hughes wrote: >> Mmmh... Since the crash seems to occur in an error handler, that could >> be the case. If I understand correctly, you're saying that distcc >> attempts to jump to an unitialized value. Doesn't Valgrind detect that >> an uninitialized valure is user as an addres to jump to? > > If the pointer is undefined and valgrind realises that it is undefined > then it should warn you. It could be well defined but bogus however, in > which case valgrind wouldn't be able to help. Just to clarify, it would warn you if: - the address given to the jump contains uninitialised bits - the address jumped to is not addressable. But if the address is wrong but initialised, and you happen to land in addressable memory (eg. in the middle of a heap block) you won't get a warning. N |