Just-In-Time Debugging
 

I weird thing just happened as I was reading the NY Times in my email. I got an error message that some value was missing or null and would I like to "Debug." I wasn't even given the opportunity to click no before this application started to run, "Just-In-Time Debuggin." Have I picked up a bot somewhat like the dastardly Xupiter? Could this possible be a legit program? Has anyone else seen this? Thanks

Doing a quick search on google, it looks like it's the debugging utility that is included with Visual Studio.

Looks like you can disable it in the registry. (msdn.microsoft.com towards the very bottom )

Sorry if this is wrong or not what you're looking for.

Many programming environments, including Borland C++ Builder, Delphi, and I think J++ Builder come with Just-In-Time Debugging.

Hm. Seems to me that using it as an error handler on an end-user desktop like that would be "Just-a-bit-too-late debugging"...

which application ran ? if it wasnt an development environment with a debugger something might be suspect, Ie has a mini debugger in it as well, that goes into some of the script editor ide's

pretty funny rat.

It says there is an error in Runtime which I don't know what that is. I suspect it this whole thing has something to do with Java but that is just a hunch.

some program crashed basically, and thats a hook to allow developers to debug it, you could try installing windows debuggung tools or such and see which program it is doing it

I downloaded and installing the debugging tools but I have no idea how to use them. The program is certainly not intutitive can someone please help me on how to use them for this problem. Much appreciated. Thanks

Go here in regedit , whats it set too ?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug

There should be a debugger key in there ?

since i have Developer studio mine looks like this

"C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\msdev.exe" -p %ld -e %ld

if not got to cmd prompt and do

drwtsn32 -I

that should enable drwatson you might have to switch on some of the options it gives.

make the error happen again, see if dr watson pops up, it should generate a log now with the info on the bad program. drwatson.log usually, or in the event log