ThomasHolz
asked on
Just-In-Time Debugging under WindowsXP
Hi,
I have a problem with the Microsoft IDE under Windows XP. The just-in-time Debugging works nicely under older OSes, like 98. Under XP it offers me the possibility to debug, even fires up the debugger, but then forces me to close my app.
Details:
- First I get the message that something bad happened, "ok" to close, "cancel" to debug. I select cancel, the debugger starts (but with the thread still running). Another message appears, saying the same as before, but this time it offers only to close the program.
- Yes, JIT-Debugging is enabled in the IDE's options...
- The current user is the admin.
Any suggestions?
I have a problem with the Microsoft IDE under Windows XP. The just-in-time Debugging works nicely under older OSes, like 98. Under XP it offers me the possibility to debug, even fires up the debugger, but then forces me to close my app.
Details:
- First I get the message that something bad happened, "ok" to close, "cancel" to debug. I select cancel, the debugger starts (but with the thread still running). Another message appears, saying the same as before, but this time it offers only to close the program.
- Yes, JIT-Debugging is enabled in the IDE's options...
- The current user is the admin.
Any suggestions?
ASKER
Good idea. Yes, if I use an int 3 exactly the same happens. No debugging possible. Perhaps it has something to do with XP? Do I have to enable JIT somewhere in the OS???
Hmm - I know that this works in W2k...
What kind of application are we talking about?
What kind of application are we talking about?
ASKER
It's just a normal MFC app I develop...
This is a known problem, I have it, and I know several others have had it. There was quite a thread going on about this in the newsgroups not so long ago.
The last post mentioned a possible fix, though I haven't tested it myself. I'll give it a go tonight and let you know if you don't respond.. The post is quoted as follows:
"Ctrl+F5 means you're not running under debugger. Does it work when you do F5? If yes, then I suspect what happens is that the breakpoint exception (which is raised when you press Cancel) is handled by XP error reporting system. You have to disable it (I think it's somewhere in My Computer properties). May be just setting the Auto value under HKLM\Software\MS\ WinNT\CurrentVersion\AEDeb
Anyway, I hope it helps you, and turns out to be alright. As far as I've heard, there is no solution that has been reported to work, but then, maybe the silence and discontinued request for help after that post indicates success...
The last post mentioned a possible fix, though I haven't tested it myself. I'll give it a go tonight and let you know if you don't respond.. The post is quoted as follows:
"Ctrl+F5 means you're not running under debugger. Does it work when you do F5? If yes, then I suspect what happens is that the breakpoint exception (which is raised when you press Cancel) is handled by XP error reporting system. You have to disable it (I think it's somewhere in My Computer properties). May be just setting the Auto value under HKLM\Software\MS\ WinNT\CurrentVersion\AEDeb
Anyway, I hope it helps you, and turns out to be alright. As far as I've heard, there is no solution that has been reported to work, but then, maybe the silence and discontinued request for help after that post indicates success...
ASKER
Hi Crius,
I didn't find any options there that helped... The Auto value in the registry is already set to 0...
I didn't find any options there that helped... The Auto value in the registry is already set to 0...
This is unfortunate. I will keep a watch out for people who discover how to get around this XP problem, though my searches thus far are mostly fruitless.
At least this seems to be a common problem...
At least this seems to be a common problem...
Dear ThomasHolz
I think you forgot this question. I will ask Community Support to close it unless you finalize it within 7 days. You can always request to keep this question open. But remember, experts can only help you if you provide feedback to their questions.
Unless there is objection or further activity, I will suggest to
"refund the points and PAQ at 0 points"
since nobody had a satisfying answer for you.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
======
Werner
I think you forgot this question. I will ask Community Support to close it unless you finalize it within 7 days. You can always request to keep this question open. But remember, experts can only help you if you provide feedback to their questions.
Unless there is objection or further activity, I will suggest to
"refund the points and PAQ at 0 points"
since nobody had a satisfying answer for you.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
======
Werner
Yeah, I've been watching the newsgroups, and there's more and more people having problems with XP and debugging as more and more people switch to it. No one has a solution yet, except give feedback to Microsoft.
It looks like a lot of different debugging issues have come up too, that only have problems on XP.
It's looking to me like XP is a bad move for developers to make at the moment.
Good luck, I suggest use F5 (debug) for now, and forget about the JIT debugger.
It looks like a lot of different debugging issues have come up too, that only have problems on XP.
It's looking to me like XP is a bad move for developers to make at the moment.
Good luck, I suggest use F5 (debug) for now, and forget about the JIT debugger.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
__asm { int 3};
?