From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: 5/5 - handle glibc pointer mangling jmp_bufs (x86/x86_64)
Date: Tue, 15 Apr 2008 12:54:00 -0000 [thread overview]
Message-ID: <20080415123103.GA32510@caradoc.them.org> (raw)
In-Reply-To: <20080414193049.GP1968@caradoc.them.org>
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
next prev parent reply other threads:[~2008-04-15 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 3:21 Pedro Alves
2008-04-07 23:02 ` Pedro Alves
2008-04-14 19:02 ` Daniel Jacobowitz
2008-04-14 19:24 ` Pedro Alves
2008-04-14 19:56 ` Daniel Jacobowitz
2008-04-15 12:54 ` Daniel Jacobowitz [this message]
2008-04-15 14:40 ` Pedro Alves
2008-04-07 6:31 Pedro Alves
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=20080415123103.GA32510@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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