Tools for identifying what a DLL provides?
I have a DLL from a manufacturer that I don't have the source for, nor do I have the header or the import library for. Since Wine developers frequently have to reverse engineer what a given DLL provides, does anybody have a good recommendation for a tool that can scan the DLL and report what functions it exports, and their arg types and return types?
Hi, On Mon, Feb 28, 2005 at 09:48:40AM -0600, David D. Hagood wrote:
I have a DLL from a manufacturer that I don't have the source for, nor do I have the header or the import library for.
Since Wine developers frequently have to reverse engineer what a given DLL provides, does anybody have a good recommendation for a tool that can scan the DLL and report what functions it exports, and their arg types and return types?
You really want http://www.dependencywalker.com/ , trust me. But probably http://www.pe-explorer.com/ is very useful, too... Or maybe even winedump... Andreas Mohr
On February 28, 2005 08:55 am, Andreas Mohr wrote:
Hi,
On Mon, Feb 28, 2005 at 09:48:40AM -0600, David D. Hagood wrote:
I have a DLL from a manufacturer that I don't have the source for, nor do I have the header or the import library for.
Since Wine developers frequently have to reverse engineer what a given DLL provides, does anybody have a good recommendation for a tool that can scan the DLL and report what functions it exports, and their arg types and return types?
You really want http://www.dependencywalker.com/ , trust me.
But probably http://www.pe-explorer.com/ is very useful, too...
Or maybe even winedump...
Andreas Mohr
Yes, but they aren't going to throw the arguments and return types out are they? The only way to do that, surely, is disassembly to see what is referenced off the stack and returned? -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed
Hi, On Mon, Feb 28, 2005 at 09:52:06AM -0800, Bill Medland wrote:
Yes, but they aren't going to throw the arguments and return types out are they? The only way to do that, surely, is disassembly to see what is referenced off the stack and returned? In the case of C, that has to be done, yes. In the case of C++, you've got function name mangling to include the function's parameters as well (as you most likely know anyway).
Andreas Mohr
Andreas Mohr wrote:
On Mon, Feb 28, 2005 at 09:48:40AM -0600, David D. Hagood wrote:
I have a DLL from a manufacturer that I don't have the source for, nor do I have the header or the import library for.
Since Wine developers frequently have to reverse engineer what a given DLL provides, does anybody have a good recommendation for a tool that can scan the DLL and report what functions it exports, and their arg types and return types?
You really want http://www.dependencywalker.com/ , trust me.
But probably http://www.pe-explorer.com/ is very useful, too... This would be probably good additions to the Wine resource page ...
bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart
participants (4)
-
Andreas Mohr -
Bill Medland -
David D. Hagood -
Michael Stefaniuc