From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: teawater@gmail.com, gdb@sourceware.org
Subject: Re: Does gdb can handle longjmp in i386 and amd64 now?
Date: Wed, 02 Sep 2009 15:22:00 -0000 [thread overview]
Message-ID: <m33a75pe16.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200909021516.n82FGlTf017321@brahms.sibelius.xs4all.nl> (Mark Kettenis's message of "Wed, 2 Sep 2009 17:16:47 +0200 (CEST)")
>>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
Mark> I think it was the fact that it requires GDB to dig into glibc
Mark> internals in combination with Ulrich Drepper no wanting to commit
Mark> keeping those internals consistent.
Oh, yeah, I forgot about the randomness and confused the current
situation with a bug report I sent about gdb not working even with the
LD_POINTER_GUARD=0 case:
http://sourceware.org/bugzilla/show_bug.cgi?id=9832
In that case I think we can safely teach gdb about the mangling.
In other cases, I don't know what to do. Continue to lose, I guess.
Tom
next prev parent reply other threads:[~2009-09-02 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 14:22 Hui Zhu
2009-09-02 15:12 ` Tom Tromey
2009-09-02 15:17 ` Mark Kettenis
2009-09-02 15:22 ` Tom Tromey [this message]
2009-09-03 1:44 ` Hui Zhu
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=m33a75pe16.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=teawater@gmail.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