From: Brian Dessent <brian@dessent.net>
To: binutils@sourceware.org
Subject: Re: Retrieving exported symbols from a dll
Date: Mon, 17 Jul 2006 20:03:00 -0000 [thread overview]
Message-ID: <44BBECF9.C0CCB55E@dessent.net> (raw)
In-Reply-To: <44BB925E.1070206@hccnet.nl>
Erik Leunissen wrote:
> I want a list of symbols that are exported from a dll (pei-i386 format).
> My first inclination was to look for an option to dlltool or objdump
> that is specifically aimed for that purpose, but did not find it.
>
> Therefore, I tend to revert to doing "objdump -x foo.dll" and scan the
> output using a home grown recipe. However, that is not nearly as
> straightforward as what I was looking for.
>
> Am I right to start from "objdump -x foo.dll", or is there something
> more straightforward?
It's not exactly on-topic for this list but the mingw project has a
(GPL) utility 'pexports' which does exactly this. Its output is a list
of the exports of the DLL, in .DEF file format.
Brian
next prev parent reply other threads:[~2006-07-17 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 13:36 Erik Leunissen
2006-07-17 20:03 ` Brian Dessent [this message]
2006-07-17 20:56 ` Danny Smith
2006-07-17 23:44 ` Christopher Faylor
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=44BBECF9.C0CCB55E@dessent.net \
--to=brian@dessent.net \
--cc=binutils@sourceware.org \
/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).