How to question about stepping into a dll
-
Windows Xp,Visual studio 6 service pack 3, Win32 c++dll Have a C++ driver and it calls the dll in a loop. The code executes once and crashes before it gets around to the top of the loop. So...I would like to know how to step into the code of the dll. I have the code in a different project. One time i accidentally did this so i know it can be done BUT i don't recall how. Googling is not very enlightening atm :^)
-
Windows Xp,Visual studio 6 service pack 3, Win32 c++dll Have a C++ driver and it calls the dll in a loop. The code executes once and crashes before it gets around to the top of the loop. So...I would like to know how to step into the code of the dll. I have the code in a different project. One time i accidentally did this so i know it can be done BUT i don't recall how. Googling is not very enlightening atm :^)
-
If it's your DLL then just create a debug version, link to it and run your program through the debugger. Set a breakpoint at some appropriate location in order to step into the DLL.
Just say 'NO' to evaluated arguments for diadic functions! Ash
AND if the DLL is dynamically, laoded, go to the part of the development environment that lets you set up DLL to be loaded early, otherwise your breakpoint will start off disabled. Worst case, temporarily hard code a DebugBreak in the loop and when that is hit, the system will drop you into the debugger.
-
Windows Xp,Visual studio 6 service pack 3, Win32 c++dll Have a C++ driver and it calls the dll in a loop. The code executes once and crashes before it gets around to the top of the loop. So...I would like to know how to step into the code of the dll. I have the code in a different project. One time i accidentally did this so i know it can be done BUT i don't recall how. Googling is not very enlightening atm :^)
If your calling program is managed code and the DLL is unmanaged, you need to go to the project properties, Debug tab, and click the "Enable unmanaged code debugging" check box.
-
AND if the DLL is dynamically, laoded, go to the part of the development environment that lets you set up DLL to be loaded early, otherwise your breakpoint will start off disabled. Worst case, temporarily hard code a DebugBreak in the loop and when that is hit, the system will drop you into the debugger.