Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Skip "special" symbols when reading minimal symbols
Date: Fri, 25 Mar 2005 20:51:00 -0000	[thread overview]
Message-ID: <20050325205203.GA25765@nevyn.them.org> (raw)
In-Reply-To: <4230E1E3.5080605@redhat.com>

On Thu, Mar 10, 2005 at 04:10:11PM -0800, Michael Snyder wrote:
> Daniel Jacobowitz wrote:
> >Nick recently introduced a hook in bfd to allow a target to mark a symbol 
> >as
> >"special".  What exactly "special" means isn't well defined, except that
> >they are not normal symbols, and objdump and nm will decline to display 
> >them
> >unless an additional command line option is given.  So, I would like to 
> >make
> >that the default behavior in GDB also.
> >
> >GDB could make use of special symbols in a target-specific fashion - in 
> >this
> >case, to build up a PC -> ISA mapping.  The most logical way to do this
> >would be to call a gdbarch hook for special symbols (or for all symbols?).
> >But we don't need that yet, so I haven't added the hook.
> >
> >The advantage of skipping the mapping symbols is that they generally occur
> >at the same addresses as other non-mapping symbols.  This causes GDB to 
> >show
> >"$a" in disassembly instead of "main" in some cases (depending on the
> >vagaries of hashing).  Whatever target-specific meaning a special symbol 
> >may
> >have, the BFD hook indicates that it isn't a standard symol, so I think 
> >it's
> >appropriate to skip it in GDB.
> >
> >Is this patch OK?  Fixes a number of testsuite failures on arm-linux and
> >arm-netbsd.
> >
> 
> I assume, if the hook is defined, you would just call it before (or
> instead of) skipping the symbol?  Maybe the hook return value (true
> or false) could tell elfread whether to skip the symbol or save it?
> In case it might be useful later?

Yes, precisely.

> I think the idea is sound, but since I've no idea what these are
> intended for (currently or in the future), it's hard to say whether
> defaulting to omit them is the right thing.

The only current user is the one I described above: ARM binaries
contain $a (ARM), $t (THUMB), and $d (data) markers in their symbol
table.  I definitely want these omitted, since they otherwise show up
as function names in disassembly.

Meanwhile, I've committed this pending patch to csl-arm-20050325-branch.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-03-25 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 17:36 Daniel Jacobowitz
2005-03-11  0:10 ` Michael Snyder
2005-03-25 20:51   ` Daniel Jacobowitz [this message]
2006-02-20 17:32 ` 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=20050325205203.GA25765@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@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