Debugging DLL loaded with LoadLibrary
-
All right, I give up. There must be a trick to this. Basically I have this gigantic workspace with projects that spits out little DLLs. Some of the basic DLLs are loaded by another DLL which is finally loaded by the executable file. What happens when I put a breakpoint is that the Visual Studio spits out warning the breakpoint is disabled. I already put in all the DLLs under the "additional DLL" under Debug tab in MS VC 6.0, and still no luck. Any help is appreciated!! :confused: Frank
-
All right, I give up. There must be a trick to this. Basically I have this gigantic workspace with projects that spits out little DLLs. Some of the basic DLLs are loaded by another DLL which is finally loaded by the executable file. What happens when I put a breakpoint is that the Visual Studio spits out warning the breakpoint is disabled. I already put in all the DLLs under the "additional DLL" under Debug tab in MS VC 6.0, and still no luck. Any help is appreciated!! :confused: Frank
Are the DLL's compiled as Debug Builds? Neville Franks, Author of Surfulater www.surfulater.com "Save what you Surf" and ED for Windows www.getsoft.com
-
Are the DLL's compiled as Debug Builds? Neville Franks, Author of Surfulater www.surfulater.com "Save what you Surf" and ED for Windows www.getsoft.com
Yes they are. Thinking a little bit more about it, I dont know if this matters, but these DLLs are being copied to another directory instead of being used straight from their respective Debug directory. So instead being run from "MyProj\Debug\MyProj.dll" there is a post-build step to "copy MyProj\Debug\MyProj.dll c:\output\dlls". Thus the code loads the Dll like LoadLibrary("c:\output\dlls\MyProj.dll")