|
From: Jeremy F. <je...@go...> - 2004-07-15 23:33:38
|
On Thu, 2004-07-15 at 23:44 +0100, Tom Hughes wrote: > Somebody did manage to reach that code however, although I'm not > quite sure how. See bug 80932 where I was also trying to work out > what that bit in the SEGV handler was for. Hm. The code should probably check to see if the tool defines init_shadow_page, and just pass it through like a normal SIGSEGV if not. But the client could only get here using --pointercheck=no anyway, so it means that all of Valgrind is vulnerable to wild pointers. J |