Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: fake symbols to aid debugging
Date: Tue, 29 Jul 2003 12:48:00 -0000	[thread overview]
Message-ID: <20030729124841.GA7393@nevyn.them.org> (raw)
In-Reply-To: <20030729033451.GJ27145@bubble.sa.bigpond.net.au>

On Tue, Jul 29, 2003 at 01:04:51PM +0930, Alan Modra wrote:
> On Mon, Jul 28, 2003 at 11:11:07PM -0400, Daniel Jacobowitz wrote:
> > Would it be feasible for the linker to
> > generate a DWARF compilation unit for these stubs, and fill it with
> > DW_AT_trampoline markers?
> 
> Yes, I could do that.  Doesn't solve my disassembly problem though,
> does it?  Even if gdb is clever enough to rummage through dwarf info
> for calls via stubs, I'd like to have objdump -d print useful symbols.

Well, yes and no.

Right now GDB only uses the minimal (ELF) symbol table when printing
symbols in disassembly.  We'd need to make it use the debug info.  I
think that's reasonable.  Making objdump do the same thing would
probably not be hard.  It wouldn't need a full reader, just one which
scanned top-level entities looking for subprograms and could parse
DW_AT_ranges or DW_AT_high/low_pc

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-07-29 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29  2:33 Alan Modra
2003-07-29  3:11 ` Daniel Jacobowitz
2003-07-29  3:34   ` Alan Modra
2003-07-29 12:48     ` Daniel Jacobowitz [this message]
2003-07-29  6:50 ` Nick Clifton
2003-07-29  8:11   ` Alan Modra

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=20030729124841.GA7393@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.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