I’d like to add logging to our unit tests that records the DLLs they use, and where they’re loaded from.
I can get the information I need from Sysinternals ListDLLs, but I’d need to run that while the test process is running, and I’d end up with race conditions: for instance, ListDLLs could run too early, and miss a DLL that’s loaded half-way through the test run; or ListDLLs could run too late, after the test process exits.
Similarly, I can get the information I need from the Visual Studio debugger’s Output and Modules windows, but I’d like to automate this on our build server.
Is there any command line tool that can run an arbitrary EXE, track the DLLs it uses, and log the information to a file?
You may write your own tool, which will use “debugging” features. This tool must
http://msdn.microsoft.com/en-us/library/windows/desktop/ms679302(v=vs.85).aspx