From: "Daniel Bonekeeper" <thehazard@gmail.com>
To: Mihai Dontu <mdontu@bitdefender.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: link table
Date: Wed, 12 Jul 2006 17:15:02 -0400 [thread overview]
Message-ID: <e1e1d5f40607121415p4e5a5c95h1011999ee27a8b57@mail.gmail.com> (raw)
In-Reply-To: <44AA7BCE.8050107@bitdefender.com>
On 7/4/06, Mihai Dontu <mdontu@bitdefender.com> wrote:
> Hi,
>
> Does anyone know a tool which I can use to dump the link table?
>
> Basically I want to know how symbols were resolved. Such a tool should
> display:
> - the name of the symbol
> - the type of the symbol (T,U - see man nm)
> - the address of the symbol (as set by the dynamic linker)
> - the module in which this the symbol's address is located
>
> Eg:
>
> myprocess
> U strcmp 0x0040500f (/lib/libc.so)
>
> Why do I want such a tool?
> - I have this program that loads several shared objects (plugins) and
> sometimes the linker resolves the syms in a wrong way making the program
> misbehave (i.e. some plugins have syms with the same name, but they do
> different things - I can not change this because the plugins are third
> party (and closed source)).
>
> Thanks in advance.
>
> M.D.
>
>
> --
> This message was scanned for spam and viruses by BitDefender.
> For more information please visit http://www.bitdefender.com/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
You can find this on objdump(1) source codes.
Daniel
--
What this world needs is a good five-dollar plasma weapon.
prev parent reply other threads:[~2006-07-12 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 14:31 link table Mihai Dontu
2006-07-12 21:15 ` Daniel Bonekeeper [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=e1e1d5f40607121415p4e5a5c95h1011999ee27a8b57@mail.gmail.com \
--to=thehazard@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=mdontu@bitdefender.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 NNTP newsgroup(s).