From: Ian Lance Taylor <iant@google.com>
To: "Rob Keeney" <robkeeney@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: ld link map file format
Date: Wed, 16 May 2007 14:48:00 -0000 [thread overview]
Message-ID: <m3ejlgsu4d.fsf@localhost.localdomain> (raw)
In-Reply-To: <28e2f86d0705160628r4d20e386gf674193655126690@mail.gmail.com>
"Rob Keeney" <robkeeney@gmail.com> writes:
> I have searched and searched and have not been able to find any
> documentation of the map file format output by ld. I need to know if
> there is anyway to determine if a symbol is a function, and if a
> symbol was provided by the linker.
The linker is part of the GNU binutils, not gcc, and questions about
it should be directed to the binutils@sourceware.org mailing list.
See http://sourceware.org/binutils/.
The map file does not tell you whether a symbol is a function. You
can of course use objdump or readelf on the linked executable to find
that out.
The map file will tell you whether a symbol was defined by the linker:
it will be in a section not associated with any input file, and will
have a linker script command on it. E.g.,
0x08049578 _end = .
Ian
prev parent reply other threads:[~2007-05-16 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 13:28 Rob Keeney
2007-05-16 14:48 ` Ian Lance Taylor [this message]
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=m3ejlgsu4d.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=robkeeney@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).