|
From: Nicholas N. <nj...@ca...> - 2004-08-26 13:13:41
|
On Thu, 26 Aug 2004, Dimitri Papadopoulos-Orfanos wrote: > For your information, I've also attempted to instrument the code with > Insure++. It didn't prove very helpful either... Something seems to be wrong > in a timeout signal handler in distcc. One thing you could try: modify Valgrind so that when the assert triggers, you print out the value of "eip". Then, use "objdump -d" to look at the original machine code (if it's in a shared object it's a little trickier to work out how the 'eip' maps to the code) and see if it really is a nested "enter" instruction. That would at least determine, with some confidence, whether it's a nested "enter" or a jump into non-code that's troubling Valgrind. N |