Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: User Thinker <thinker@branda.to>
Cc: gdb-patches@sourceware.org, mokoko-group@googlegroups.com
Subject: Re: Get backtrace at PLT and stepi into PLT
Date: Thu, 16 Jul 2009 19:11:00 -0000	[thread overview]
Message-ID: <20090716113730.GA8646@caradoc.them.org> (raw)
In-Reply-To: <19038.65134.58926.218902@bibi.branda.to>

On Thu, Jul 16, 2009 at 06:18:22PM +0800, User Thinker wrote:
> Hi all,
> 
> I have a patch that makes GDB can properly stepi into PLT for ARM Thumb
> instruction.  The patch also allow GDB to perform backtrace at PLT.

What version of GDB are these patches against?  Have you tried the
version from CVS?  This should work perfectly.

> It means GDB should put a invalid instruction of Thumb version at
> base address of the trampoline.  But, it actually puts
> ARM version one.  I have checked GDB source code for this issue.
> GDB check flags in symbol that contain memory space that breakpoint
> was setted at.  If the symbol is flaged as Thumb, it uses
> Thumb version invalid instruction code, or it would use
> ARM version.  It is reasonable.  But, the trampoline in PLT contains
> both types of instructions.  And, the result of checking is
> the block where the trampoline is in is not Thumb.

The CVS version of GDB checks ABI-defined mapping symbols ($a, $t).
These also allow disassembly to work correctly.

> 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?

> begin 644 arm-plt.diff.gz
> M'XL(`#OJ7DH``YU7;4_;2!#^C'_%E)-Z`3O43D*20JDH$"A5"%62ZGKWQ?++

Please include patches as text.  See the list archives for examples.
Thanks.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-07-16 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 19:07 User Thinker
2009-07-16 19:11 ` Daniel Jacobowitz [this message]
     [not found]   ` <19040.7376.886250.727782@bibi.branda.to>
     [not found]     ` <bc7444e5-0719-4ee1-acbb-4495ded392a6@a37g2000prf.googlegroups.com>
2009-07-17  8:47       ` Fwd: " Thinker Li
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
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

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=20090716113730.GA8646@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mokoko-group@googlegroups.com \
    --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