Just-In-Time Debugging

2007-05-30 09:46:10

#1

liquidat0r: wtf.; +2,223|7098|UK

What the hell is this? And more importantly, why the hell did it appear?

I was quite happily sitting on my PC when all of a sudden, this pops up:

https://img255.imageshack.us/img255/2619/justintimeuh1.png

I was running Ventrilo, Notepad, FileZilla, Dreamweaver, Xfire, BF2CC and a couple of instances of Windows Explorer.

I never though I'd find my self asking a question about Windows, but: here I am.

2007-05-30 09:48:44

#2

Thoruz: Member; +42|6797|Germany

http://msdn2.microsoft.com/en-us/library/5hs4b7a6.aspx all i could find about that

2007-05-30 09:48:52

#3

max: Vela Incident; +1,652|7038|NYC / Hamburg

Microsoft wrote:
ust-In-Time debugging is a feature that launches the Visual Studio debugger automatically when a program, running outside Visual Studio, encounters a fatal error. Just-In-Time debugging allows you to examine the error before the application is terminated by the operating system. The Visual Studio debugger does not need to be running when the error occurs.

I also sometimes get that error. Just click it away and probs nothing will happen

EDIT: dang, couple of secs

Last edited by max (2007-05-30 09:49:15)

_{once upon a midnight dreary, while i pron surfed, weak and weary, over many a strange and spurious site of ' hot xxx galore'. While i clicked my fav'rite bookmark, suddenly there came a warning, and my heart was filled with mourning, mourning for my dear amour, " 'Tis not possible!", i muttered, " give me back my free hardcore!"..... quoth the server, 404.}

2007-05-30 09:49:45

#4

liquidat0r: wtf.; +2,223|7098|UK

I guess it came from BF2CC then? (.NET Framework)

2007-05-30 09:49:53

#5

[THE] comben: Wee and Biscuits; +43|7004|Cardiff

this might help

http://msdn2.microsoft.com/en-us/library/5hs4b7a6.aspx

edit: lol out googled

Last edited by [THE] comben (2007-05-30 09:50:29)

2007-05-30 09:52:07

#6

liquidat0r: wtf.; +2,223|7098|UK

Thanks for those links.

Actually, it's Xfire. Xfire has disappeared from my processes list -- but I can still see it, (but not use it).

I just clicked 'Yes' btw, the normal solution to random Windows errors.

2007-05-30 09:52:11

#7

max: Vela Incident; +1,652|7038|NYC / Hamburg

liquidat0r wrote:
I guess it came from BF2CC then? (.NET Framework)

anything crash? I think its a little oversensitive. I used to get it a lot before I reformatted but never noticed any program crashing or shutting down.

EDIT: ahh, try reinstalling/updating xfire maybe

Last edited by max (2007-05-30 09:52:47)

_{once upon a midnight dreary, while i pron surfed, weak and weary, over many a strange and spurious site of ' hot xxx galore'. While i clicked my fav'rite bookmark, suddenly there came a warning, and my heart was filled with mourning, mourning for my dear amour, " 'Tis not possible!", i muttered, " give me back my free hardcore!"..... quoth the server, 404.}

2007-05-30 09:54:18

#8

liquidat0r: wtf.; +2,223|7098|UK

Yup. Xfire is broken. *reinstall*

Interestingly, Xfire updated itself earlier -- this is the first time I had run it, since update.

2007-05-30 09:57:33

#9

max: Vela Incident; +1,652|7038|NYC / Hamburg

liquidat0r wrote:
Yup. Xfire is broken. *reinstall*

Interestingly, Xfire updated itself earlier -- this is the first time I had run it, since update.

not the first time that xfire released a buggy patch. I've had one a few versions back that caused my whole pc to be unstable. The next version fixed it though. Also its always possible that it somehow didn't update correctly

_{once upon a midnight dreary, while i pron surfed, weak and weary, over many a strange and spurious site of ' hot xxx galore'. While i clicked my fav'rite bookmark, suddenly there came a warning, and my heart was filled with mourning, mourning for my dear amour, " 'Tis not possible!", i muttered, " give me back my free hardcore!"..... quoth the server, 404.}

2007-05-30 10:29:09

#10

topal63: . . .; +533|7189

JIT is part of the .NET platform.

When I program in C++ or C#; and code for the .NET platform; it is not complied into binary machine code. It is compiled into .NET pseudo-code. When the code executes the pseudo-code is converted into binary on the fly (Just In Time : JIT). There is either a bug in the pseudo code or there is an error in the .NET installation.

1.) Sometimes restarting windows will fix the .NET problem (if something has run amuck here).
2.) .NET programs are compiled for specific .NET releases (you might need older ones installed for compatibility).
3.) The JIT pseudo-code compile error might go away - if the offending .NET program is reinstalled.

Last edited by topal63 (2007-05-31 10:03:05)

2007-05-30 10:46:31

#11

liquidat0r: wtf.; +2,223|7098|UK

Wow, very knowledgeable there, topal

BF2S Forums Just-In-Time Debugging

Microsoft wrote:

liquidat0r wrote:

liquidat0r wrote:

Board footer