public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: "Paulo J. Matos" <pocmatos@gmail.com>
Cc: binutils@sources.redhat.com
Subject: Re: synthetic symtab on bfd
Date: Mon, 01 Nov 2010 16:02:00 -0000	[thread overview]
Message-ID: <20101101160205.GA28366@caradoc.them.org> (raw)
In-Reply-To: <86aaltkpwb.fsf@pm18pc01.europe.root.pri>

On Mon, Nov 01, 2010 at 03:46:44PM +0000, Paulo J. Matos wrote:
> 
> On bfd there's a function (which doesn't seem to be documented):
> - bfd_get_synthetic_symtab
> 
> What is this synthetic symbol table?

Symbols that aren't in the object file, but BFD can infer and finds
useful.  For instance, most platforms don't put a symbol on each PLT
entry.  But disassembly is more useful if it says "branch to
memcpy@plt" instead of "branch to _init - 0x54".

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2010-11-01 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 15:50 Paulo J. Matos
2010-11-01 16:02 ` Daniel Jacobowitz [this message]
2010-11-01 18:18   ` Paulo J. Matos

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=20101101160205.GA28366@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=binutils@sources.redhat.com \
    --cc=pocmatos@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).