When I was debugging our application with WinDbg, I saw a 7 messages like this for different assemblies:
* MyApp second chance resolve: Requested assembly: "Newtonsoft.Json, Version=13.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed"
* MyApp second chance resolve: Trying to load: "C:\MyApp\Newtonsoft.Json.dll"
ModLoad: 000002a7`366b0000 000002a7`36760000 Newtonsoft.Json.dll
ModLoad: 000002a7`36760000 000002a7`36810000 Newtonsoft.Json.dll
* MyApp second chance resolve: Loaded assembly: "Newtonsoft.Json, Version=13.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed"
However, in the list of loaded modules, it appears only once, at the latter address:
1:003> lm m Newtonsoft*
Browse full module list
start end module name
000002a7`36760000 000002a7`36810000 Newtonsoft_Json_2a736760000 (deferred)
Using Process Monitor, I could confirm that our application is accessing both DLLs and I could figure out the full path of both DLLs. However, that required reproducing the issue, including the restart of 2 executables.
Is it possible to configure WinDbg to show the full path of the DLL being loaded during a ModLoad event? How?