From: adeeshah <asgher.adeel@gmail.com>
To: gdb@sourceware.org
Subject: How to check that GDB is going to make a longjmp?
Date: Wed, 07 Sep 2011 09:10:00 -0000 [thread overview]
Message-ID: <32414505.post@talk.nabble.com> (raw)
Hi,
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?
Adeel.
--
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.
next reply other threads:[~2011-09-07 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 9:10 adeeshah [this message]
2011-09-07 9:33 ` Kevin Pouget
2011-09-13 13:28 ` adeeshah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32414505.post@talk.nabble.com \
--to=asgher.adeel@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox