* ld link map file format
@ 2007-05-16 13:28 Rob Keeney
2007-05-16 14:48 ` Ian Lance Taylor
0 siblings, 1 reply; 2+ messages in thread
From: Rob Keeney @ 2007-05-16 13:28 UTC (permalink / raw)
To: gcc-help
Hi,
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.
Any help will be greatly appreciated!
Thanks!
--
--- Rob Keeney / robkeeney@gmail.com ---
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: ld link map file format
2007-05-16 13:28 ld link map file format Rob Keeney
@ 2007-05-16 14:48 ` Ian Lance Taylor
0 siblings, 0 replies; 2+ messages in thread
From: Ian Lance Taylor @ 2007-05-16 14:48 UTC (permalink / raw)
To: Rob Keeney; +Cc: gcc-help
"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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-05-16 14:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-16 13:28 ld link map file format Rob Keeney
2007-05-16 14:48 ` Ian Lance Taylor
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).