5/5 - handle glibc pointer mangling jmp_bufs (x86/x86_64)

Daniel Jacobowitz drow@false.org
Tue Apr 15 12:54:00 GMT 2008


On Mon, Apr 14, 2008 at 03:30:49PM -0400, Daniel Jacobowitz wrote:
> You could do this even more evilly.  Do it by setting a breakpoint on
> setjmp, recording information before and after, and then deleting the
> breakpoint until we re-run.  Yes, this is getting excessive.  But
> there shouldn't ever be a call to longjmp without a call to setjmp
> first.

Thinking about this more, how hard would it be to single-step through
longjmp instead?  I'm sure there will be some platform where it
doesn't work, and that platform can use the current get_longjmp_target
mechanism, but for glibc platforms we could just step and see where we
end up, then decide whether to continue or stop.

-- 
Daniel Jacobowitz
CodeSourcery



More information about the Gdb-patches mailing list