It can list the functions that’s used among the exported functions.
How does it do the trick?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It can list the functions that’s used among the exported functions.
How does it do the trick?
The key is that every Windows module (both executables and libraries) contains an import table that lists all of the other modules that it depends on. This table is built by the linker and is used by the operating system internally to determine the dependencies of the module and load the appropriate libraries.
So all that Dependency Walker has to do is recurse through all of those modules (figuratively, “walking” through them), building a list of the modules specified in their respective import tables.
It does not display all of the run-time dependencies (such as those loaded with the
GetProcAddressfunction), as those are not listed in the import table. It only shows the load-time (or static) dependencies.You can find more information about how Dependency Walker works here and here.