Solved

Just-In-Time Debugging under WindowsXP

Posted on 2002-06-12
10
307 Views
Last Modified: 2010-04-02
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?
0
Comment
Question by:ThomasHolz
  • 3
  • 3
  • 2
  • +2
10 Comments
 
LVL 86

Expert Comment

by:jkr
ID: 7073792
Does this also happen when you place an EXCEPTION_BREAKPOINT in your code, e.g.

__asm { int 3};

?
0
 

Author Comment

by:ThomasHolz
ID: 7073938
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???
0
 
LVL 86

Expert Comment

by:jkr
ID: 7074101
Hmm - I know that this works in W2k...

What kind of application are we talking about?
0
 

Author Comment

by:ThomasHolz
ID: 7074731
It's just a normal MFC app I develop...
0
 
LVL 3

Expert Comment

by:Crius
ID: 7075882
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\AEDebug key to 0 will be enough, though I'm not sure if it's still used in XP and how it's related to error reporting."

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...
0
Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

 

Author Comment

by:ThomasHolz
ID: 7077516
Hi Crius,

I didn't find any options there that helped... The Auto value in the registry is already set to 0...
0
 
LVL 3

Expert Comment

by:Crius
ID: 7078525
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...
0
 
LVL 11

Expert Comment

by:griessh
ID: 7262270
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
0
 
LVL 3

Expert Comment

by:Crius
ID: 7262305
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.
0
 
LVL 6

Accepted Solution

by:
Mindphaser earned 0 total points
ID: 7332932
Points refunded and moved to PAQ

** Mindphaser - Community Support Moderator **
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Article by: SunnyDark
This article's goal is to present you with an easy to use XML wrapper for C++ and also present some interesting techniques that you might use with MS C++. The reason I built this class is to ease the pain of using XML files with C++, since there is…
Written by John Humphreys C++ Threading and the POSIX Library This article will cover the basic information that you need to know in order to make use of the POSIX threading library available for C and C++ on UNIX and most Linux systems.   [s…
The goal of the video will be to teach the user the concept of local variables and scope. An example of a locally defined variable will be given as well as an explanation of what scope is in C++. The local variable and concept of scope will be relat…
The viewer will learn how to pass data into a function in C++. This is one step further in using functions. Instead of only printing text onto the console, the function will be able to perform calculations with argumentents given by the user.

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now