From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
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:17:00 -0000 [thread overview]
Message-ID: <200909021516.n82FGlTf017321@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <m37hwhpei0.fsf@fleche.redhat.com> (message from Tom Tromey on Wed, 02 Sep 2009 09:12:23 -0600)
> From: Tom Tromey <tromey@redhat.com>
> Date: Wed, 02 Sep 2009 09:12:23 -0600
>
> >>>>> ">" == Hui Zhu <teawater@gmail.com> writes:
>
> >> I try the following code with gdb in i386 and amd64:
>
> This is http://sourceware.org/bugzilla/show_bug.cgi?id=9270. glibc's PC
> mangling confuses gdb. Pedro has a patch for this; I keep forgetting
> what is holding it back.
I think it was the fact that it requires GDB to dig into glibc
internals in combination with Ulrich Drepper no wanting to commit
keeping those internals consistent.
next prev parent reply other threads:[~2009-09-02 15:17 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 [this message]
2009-09-02 15:22 ` Tom Tromey
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=200909021516.n82FGlTf017321@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sourceware.org \
--cc=teawater@gmail.com \
--cc=tromey@redhat.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