|
Latest Articles
Sep 3, 2008
Aug 5, 2008
Jul 29, 2008
Accounts Area
Are you a vendor?
If you are a vendor for any software listed in our catalogue, you can get full control over your listing by contacting us.You can also submit your 64-bit software today for free! |
DLL Export Viewer v1.10
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.
REPORT US: This software is not 64-bit native!!!
Comments
|
Our Directories
Free Link World - free SE and User friendly general directory.Free General Directory - free general directory with easy acceptance of quality resources. No registration and back link needed. Search Engine Friendly Directory - general free link directory. Links by Google
Ads by Google
|


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.

