From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFC] i386 PLT stub unwinder
Date: Mon, 13 Jun 2011 19:15:00 -0000 [thread overview]
Message-ID: <201106131915.p5DJFESL000868@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <m362o9u1g7.fsf@fleche.redhat.com> (message from Tom Tromey on Mon, 13 Jun 2011 10:43:20 -0600)
> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 13 Jun 2011 10:43:20 -0600
>
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> On Mon, 13 Jun 2011 17:55:56 +0200, Mark Kettenis wrote:
> >> Jan's mail about DWARF CFI for PLT stubs prompted me to write an
> >> undinder for the PLT stubs as defined by the i386 ABI. With this
> >> change I can step through the PLT stubs and always have a proper
> >> backtrace.
>
> Jan> I do not think GDB is the right place to fix it, it should be fixed
> Jan> by proper .eh_Frame as this problem affects all the tools trying to
> Jan> unwind such as also oprofile, systemtap etc.
Sure, fixing this in ld is better. But that will only work if people
use a full GNU toolchain.
> I agree, but I think also doing it in GDB is harmless, at least provided
> that the new unwinder is only applied when the PLT stubs are missing the
> needed info. That way, when ld is fixed, GDB will automatically start
> doing the right thing.
Yes. The DWARF CFI unwinder comes before the PLT stub unwinder in the
list, so if there is CFI for the PLT stubs, it will be used instead.
So there is no harm in adding this functionality to GDB.
next prev parent reply other threads:[~2011-06-13 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 15:56 Mark Kettenis
2011-06-13 16:14 ` Jan Kratochvil
2011-06-13 16:32 ` Joel Brobecker
2011-06-13 16:43 ` Tom Tromey
2011-06-13 19:15 ` Mark Kettenis [this message]
2011-06-14 11:49 ` Pedro Alves
2011-06-14 11:53 ` 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=201106131915.p5DJFESL000868@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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