Hi,
I have a program that dynamically loads a DLL and starts a thread from that DLL...
I need to debug & step through the thread in that DLL, but I can't connect to it.
If I run the .exe in the debugger, I can't set a breakpoint in the DLL since it's in a different project.
I tried "Attach to Process", but once I select my program to attach to, it closes the DLL project, then says "Cannot execute program".
Nevermind. I figured out how to do it.
I just opened the DLL project and clicked Go (F5), then it asked me which .exe to load, so I selected my .exe and it started debugging as usual.
I'm still not sure how that "Attach to Process" is supposed to work though.
It creates new "temporary" project for the exe and starts debugging (so I prefer to do it from another instance of VS)I'm still not sure how that "Attach to Process" is supposed to work though.
If you break - it shows the current callStack, starting with some kernel addresses probably
You can go up the stack till you see the name of your own function (if exe is compiled with debug info) - when you select your own function - VS will open proper code if it can locate it in the path notedin the pdb file, otherwise it will ask about location of the source file, you can browse and select the apropriate file, after that you can debug as regular...
For dlls I sometimes add assert or MEssageBox at the beginning of the function of interest, attach debugger while I see the message, go up the stack into the function I have put the message box and place breakpoint in the next line, after that click ok and start debugging from the breakpoint
All problems in computer science can be solved by another level of indirection,
except for the problem of too many layers of indirection.
– David J. Wheeler
