From: Daniel Jacobowitz <drow@false.org>
To: Thinker Li <thinker@branda.to>
Cc: gdb-patches@sourceware.org
Subject: Re: Get backtrace at PLT and stepi into PLT
Date: Fri, 17 Jul 2009 14:26:00 -0000 [thread overview]
Message-ID: <20090717120338.GA17493@caradoc.them.org> (raw)
In-Reply-To: <19040.10633.720987.12824@bibi.branda.to>
On Fri, Jul 17, 2009 at 03:34:33PM +0800, Thinker Li wrote:
> I tried it with GDB 6.8. I had just tried the version from CVS this morning.
> It can stepi into PLT, but backtrace is still not work.
>
> I did some tests for GDB.
> I configured GDB with command
> configure --build=x86_64-unknown-linux-gnu \
> --host=x86_64-unknown-linux-gnu \
> --target=arm-eabi-linux --disable-werror
It should not matter to GDB, but you probably want arm-linux-gnueabi
there instead of arm-eabi-linux.
> > > If you try to backtrace stack when GDB stop at PLT, you would
> > > get nothing. It is because no any unwinder can handle code in PLT.
> >
> > arm_stub_unwinder_sniffer is supposed to handle this case. It's been
> > there since 2005, and I've used it successfully. What's going wrong
> > with that?
> I can not even found arm_stub_unwinder_sniffer in the source tree of
> GDB. So, where is arm_stub_unwinder_sniffer?
> Is it part of GDB, officially?
Sorry, arm_stub_unwind_sniffer.
You'll see that contains a call to in_plt_section. Is that not
working for you?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-07-17 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 8:48 Thinker Li
2009-07-17 14:26 ` Daniel Jacobowitz [this message]
[not found] ` <19040.34533.656545.753721@bibi.branda.to>
2009-07-17 15:07 ` Daniel Jacobowitz
[not found] ` <19044.7794.607077.330791@bibi.branda.to>
2009-07-20 13:15 ` Daniel Jacobowitz
2009-07-21 15:12 ` Thinker Li
2009-07-21 18:15 ` Daniel Jacobowitz
2009-07-22 12:12 ` Thinker Li
2009-07-22 15:49 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2009-07-16 19:07 User Thinker
2009-07-16 19:11 ` Daniel Jacobowitz
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=20090717120338.GA17493@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=thinker@branda.to \
/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