Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Mon, 20 Jul 2009 13:15:00 -0000	[thread overview]
Message-ID: <20090720120722.GA28313@caradoc.them.org> (raw)
In-Reply-To: <19044.7794.607077.330791@bibi.branda.to>

On Mon, Jul 20, 2009 at 03:36:18PM +0800, Thinker Li wrote:
> And, as what you had said, there are a lot of ABI-defined mapping symbols
> ($a, $t) in symbol tables of shared objects.  But, they are generated
> only for .text but .plt section.  So, it got nothing to try to issue
> a backtrace command when the inferior is stopped at .plt section.
> 
> Is GNU ld supposed to generate ABI-defined mapping symbols for
> .plt?  Or, does GDB need to do more work on this issue?

Mapping symbols are used for other things, like setting breakpoints,
but not for backtrace.  What's the actual problem with backtracing?

Current versions of GNU ld do generate correct mapping symbols for the
PLT.  Some earlier versions didn't, though.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2009-07-20 12:07 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
     [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 [this message]
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=20090720120722.GA28313@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