This is the mail archive of the
mailing list for the GDB project.
Re: How to check that GDB is going to make a longjmp?
- From: Kevin Pouget <kevin dot pouget at gmail dot com>
- To: adeeshah <asgher dot adeel at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Wed, 7 Sep 2011 11:32:16 +0200
- Subject: Re: How to check that GDB is going to make a longjmp?
- References: <firstname.lastname@example.org>
I guess you want to catch longjump of the inferior, not GDB itself, right?
One way is to set a breakpoint on the `longjmp' function itself, and
then jump over the function, or enter `return' to return directly from
the function without executing its body.
The content of the jmp_bug depends of your system, so you need to
check your local setjmp.h. For instance, you can see in this µlibC 
implementation that they use a buffer to store the relevant CPU
registers, with pre-processor macro.
setjump populates the buffer with the registers, longjmp pushes the
buffer values back to the CPU registers.
On Wed, Sep 7, 2011 at 11:10 AM, adeeshah <email@example.com> wrote:
> I want to avoid the GDB's longjmp. Is there a way to check that GDB is going
> to make a longjmp?
> How can i check the contents of jmp_buf?
> View this message in context: http://old.nabble.com/How-to-check-that-GDB-is-going-to-make-a-longjmp--tp32414505p32414505.html
> Sent from the Sourceware - gdb list mailing list archive at Nabble.com.