T
Tom Kacvinsky
Guest
I am trying to debug an issue where I _think_ the executable in question is loading two different C run times. Dependency walker shows the UCRT libraries and where they are loaded from, which is quite different than what I expecting. I read the document
Dynamic-Link Library Search Order - Win32 apps
And it appears that it is the last search algorithm that is used - referencing PATH. ON the other hand, the location of the UCRT libraries does not even show in the output window of the Visual Studio GUI, where you can see which modules are loaded. So I am thinking that the UCRT libraries are given special treatment, but I do need to know where they are coming from. I don't trust dependency walker ouput as it should find the libraries in the system locations first, and I don't trust the Visual Studio GUI because it is not showing them at all. What is the best way of finding from where the UCRT libraries are loaded?
Also, is there any reason why a manifest would matter in this case?
Continue reading...
Dynamic-Link Library Search Order - Win32 apps
And it appears that it is the last search algorithm that is used - referencing PATH. ON the other hand, the location of the UCRT libraries does not even show in the output window of the Visual Studio GUI, where you can see which modules are loaded. So I am thinking that the UCRT libraries are given special treatment, but I do need to know where they are coming from. I don't trust dependency walker ouput as it should find the libraries in the system locations first, and I don't trust the Visual Studio GUI because it is not showing them at all. What is the best way of finding from where the UCRT libraries are loaded?
Also, is there any reason why a manifest would matter in this case?
Continue reading...