AutoHotkey Community

[Rajat]

This utility displays the list of all exported functions and their virtual memory addresses for the specified DLL files.

http://www.nirsoft.net/utils/dll_export_viewer.html

(Try it on corrupt's nice Cmdret dll)
_________________

[corrupt]

Very handy. Thanks

[PhiLho]

I don't know the software you recommand, but for such functionnality and (perhaps) more, I usually use Dependency Walker which is free and powerful: it can even find runtime dependencies (LoadLibrary).

[mario_a]

This is not true. Dependencies due to LoadLibrary calls are not detected by Dependency Walker.

[PhiLho]

Maybe I wasn't clear enough.

DW doesn't detect statically dependencies created by LoadLibrary.

This is not possible, or at least extremly difficult, supposing to disassemble the code to find a call to this library. And even then, if the name of the called DLL is dynamically built, it is not possible to know it.

But if you run the analyzed program, or a program calling the analyzed DLL, DW will be able to detect a call to LoadLibrary and know which DLL is loaded (and which functions are called).

Of course, it will detect only the DLLs called at runtime: a program may dynamically depend, say on a JPeg reading library, but if you never load such image in your testing, you will not see it.

HTH.

[mario_a]

[PhiLho]