Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thinker Li <thinker@branda.to>
To: Daniel Jacobowitz <drow@false.org>
Cc: Thinker Li <thinker@branda.to>, gdb-patches@sourceware.org
Subject: Re: Get backtrace at PLT and stepi into PLT
Date: Wed, 22 Jul 2009 12:12:00 -0000	[thread overview]
Message-ID: <19046.58285.142467.788502@bibi.branda.to> (raw)
In-Reply-To: <20090721180907.GB11667@caradoc.them.org>

Daniel Jacobowitz writes:
 > On Tue, Jul 21, 2009 at 10:57:06AM +0800, Thinker Li wrote:
 > > You can not do backtrace when you stop at PLT with GDB.
 > > arm_stub_unwind_sniffer create a frame with NORMAL_FRAME type for
 > > PLT.  But, when we do backtrace, get_prev_frame() will check if
 > > this frame inside_entry_func.  Since we can not found any symbol for
 > > PLT, it:s func address is 0, and entry_point_address() is also 0 if
 > > symfile_objfile is NULL (no main symbol table).  It makes problem on
 > > backtracing.
 > 
 > Thanks, that's much clearer.  That's where the bug is.  An unknown
 > function address should not be inside_entry_func.
Is it possible that entry point of an program is 0?
Maybe, we should change interface of entry_point_address() to indicate
an unknown address.

Do you have any suggestion?


  reply	other threads:[~2009-07-22 10:02 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
2009-07-21 15:12           ` Thinker Li
2009-07-21 18:15             ` Daniel Jacobowitz
2009-07-22 12:12               ` Thinker Li [this message]
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=19046.58285.142467.788502@bibi.branda.to \
    --to=thinker@branda.to \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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