Re: Disable breakpoints inside dll
- From: "Jacob L. Anawalt" <janawalt+msnews@xxxxxxxxxxxxxxxxx>
- Date: Fri, 29 Jul 2005 10:58:20 -0600
Mandi wrote:
This dll is loaded and ran by the new exe (by using LoadLibrary) but with problems. Trying to debug it with the debugger, the exe dose run but breakpoints inside the dll become automatically disable (recompiling doesn't help).
We have a couple .exe's, one launching the other and the way we handle debugging the invoked .exe is to put a MessageBox in so the code halts at that point. We then attach to that process with the debugger, verify break points (usually having one set just after the MessageBox invocation, and click OK on the MessageBox. We don't start the calling ..exe with the IDE/Debugger, so it's not being traced. If we needed to do both, I would probably use two instances of the IDE.
I would imagine the same thing works out for your .dll, and that unless you needed to debug something that happens as soon as you attach to the DLL, you may not even need to stop the program with a MessageBox. We use it because we were debugging things that happen as the frameworks initialize.
I'm interested in learning "the right way" to handle this.
-- Jacob .
- References:
- Disable breakpoints inside dll
- From: Mandi
- Disable breakpoints inside dll
- Prev by Date: Lookup volume to physical device mappings in 98-XP
- Next by Date: RE: Virtual fodler with drive letter
- Previous by thread: Disable breakpoints inside dll
- Next by thread: Re: Disable breakpoints inside dll
- Index(es):
Relevant Pages
|
