public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* ld -Map on a shared library
@ 2004-03-25 19:20 Tremblay
  2004-03-25 19:51 ` Ian Lance Taylor
  0 siblings, 1 reply; 2+ messages in thread
From: Tremblay @ 2004-03-25 19:20 UTC (permalink / raw)
  To: gcc-help

Hi,

I'm trying to create a map file for a shared library.  The command the 
average user would expect is "ld -Map <mapfile.map> <library.so>" 
 Unfortunately, this creates a virtually empty symbol file.  I've 
already tried --cref but that doesn't actually give you the addresses of 
the functions/variables.


!!HELP!!
Chris

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: ld -Map on a shared library
  2004-03-25 19:20 ld -Map on a shared library Tremblay
@ 2004-03-25 19:51 ` Ian Lance Taylor
  0 siblings, 0 replies; 2+ messages in thread
From: Ian Lance Taylor @ 2004-03-25 19:51 UTC (permalink / raw)
  To: Tremblay; +Cc: gcc-help

Tremblay <w20777@motorola.com> writes:

> I'm trying to create a map file for a shared library.  The command the
> average user would expect is "ld -Map <mapfile.map> <library.so>"
> Unfortunately, this creates a virtually empty symbol file.  I've
> already tried --cref but that doesn't actually give you the addresses
> of the functions/variables.

The linker can create a map file when it creates a shared library.  It
won't do so given an existing shared library.

Not all the information generated in the map file when creating a
shared library is available by inspecting an existing shared library.

Ian

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-25 19:13 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-25 19:20 ld -Map on a shared library Tremblay
2004-03-25 19:51 ` 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).