8 replies to this topic

[sosaited]

This Program scans a dll (Or a folder of dll's) for the Exported Functions it contains. It does not display the paramters of the functions, Which i really need, so if someone knows about a program that can also tell the parameters of the functions please post it here

Download Dll export Viewer

Homepage

Description:

This utility displays the list of all exported functions and their virtual memory addresses for the specified DLL files. You can easily copy the memory address of the desired function, paste it into your debugger, and set a breakpoint for this memoery address. When this function is called, the debugger will stop in the beginning of this function.
For example: If you want to break each time that a message box is going to be displayed, simply put breakpoints on the memory addresses of message-box functions: MessageBoxA, MessageBoxExA, and MessageBoxIndirectA (or MessageBoxW, MessageBoxExW, and MessageBoxIndirectW in unicode based applications) When one of the message-box functions is called, your debugger should break in the entry point of that function, and then you can look at call stack and go backward into the code that initiated this API call

[PhiLho]

QuickView, which was distributed with older versions of Windows, used to display such information.
Dependency Walker can do that too, and also shows, as the name implies, the dependencies: not only it shows the DLLs statically linked by another DLL or an EXE, but it can even run an EXE and check at runtime the LoadLibrary calls, hence the dynamic dependencies.

AFAIK, I fear there is no mean to see the parameters required by a DLL function. I suppose that theoritically, it can be done by dissassemblying the code of the functions and see where in the heap they take their parameters. But it is easier and more reliable to rely on the API documentation, if available.

[Chris]

Dll export Viewer looks like a great utility. I may wind up using it to help debugging.

Thanks.

[PhiLho]

It is interesting, but as you can see in the related Web page, it relies on a database of APIs, ie. it can do nothing with an unknown/artibrary DLL. I suspected that seeing in the screenshot informations like HWND (disassembly would give only "32bit parameter", not the exact type).
This is still useful, but well, you get something similar (probably less extensive) with ApiViewer or the API-Guide.

Of course, PE Explorer has the advantage of being contextual (showing informations on the current DLL).

[AHKnow]

Another interesting free utility- Anywhere PE Viewer

http://www.ucware.com/apev/index.htm


Then there is the Microsoft online database- http://support.microsoft.com/dllhelp/

[majkinetor]

The fastest, smallest (~100K) and simplest to use:
http://physio-a.univ...ns/FILEINFO.htm

[CyberGeek]

i was just gonna post his util....

but you had already

quite handy