No JIT debugger found

i keep getting an error message telling me that "no JIT degugger found". L4 then crashes. it usually happens when i am using the passage guide. i tried using several differetn registry cleaners but it keeps coming back. has anyone else had this problem?

Find more posts tagged with

Comments

Jon

It's looking for a JIT (Just in Time?) debugger presumably for an error occurring in .NET or the platform Logos4 runs on; I've never seen this throughout the beta up till now.

It might be useful to enable logging in Logos 4, as per http://sites.google.com/site/logos4wiki/faq/troubleshooting, and posting your logs here when it crashes so the dev guys can have a look...

Also, which OS are you running on?

Howard Silverman

https://community.logos.com/discussion/comment/37884#Comment_37884

thank you for responding. i am running XP professional version 2002 sp 3 intel Core 2CPU T7600 @ 2.33 Ghz 2.00 GB of RAM

i will do as you say. i gues i am stuck until someone finds an answer. it usually happens if i am waiting on one of the guides to load.

thanks again

howard silverman

Howard Silverman

https://community.logos.com/discussion/comment/38933#Comment_38933

i made it crash but i cannot seem to copy and paste the zip file of the log onto this forum. how do i get the zip file of the log on here?

thanks

Howard Silverman

https://community.logos.com/discussion/comment/37884#Comment_37884

i made it crash and here is the zip file. i look forward to hearing if there is something i can do.

thank you. howard silverman

8561.Logos4.zip

777

i keep getting an error message telling me that "no JIT degugger found". L4 then crashes. it usually happens when i am using the passage guide. i tried using several differetn registry cleaners but it keeps coming back. has anyone else had this problem?

Hi Howard,

I do not use Microsoft Windows any longer, but you may be able to install a JIT debugger and get more clues. Microsoft offers a free trial beta of their Visual Studio 2010 Professional beta 2 from this page: http://msdn.microsoft.com/en-us/evalcenter/dd819107.aspx

You might also get a debugger that would work if you install Microsoft's Express Edition of their C# interpreter/pseudo-compiler, which you can obtain here: http://www.microsoft.com/express/vcsharp/Default.aspx

Since I haven't kept up with the new-fangled Microsoft managed executables that actually compile at run-time (compared to much smaller and faster code generated by their C++ compiler), I couldn't say if that debugger code should even be in the executables that Logos is distributing. C# and VB and most of the other Microsoft programming languages now produce what is effectively Microsoft's version of Java. In the old days we'd use C compilers and leave the debugging info in the compiled executables only for our internal testing but after we had the application debugged (and tuned up with some assembler code), we'd recompile without the debugging information, before public consumption. The executables without the debugging info were a lot smaller as well.

If you're interested, there's always a way to find out. If you install a JIT debugger you may found out a bit about the problem.

Mike

Howard Silverman

https://community.logos.com/discussion/comment/39005#Comment_39005

thank you for the assistance. if there is not harm to be had in downloading the visual studio 2010 i will try it.

here is the log from the last time L4 crashed.

8371.Logos4.zip

thnaks again

howard

TCBlack

https://community.logos.com/discussion/comment/39074#Comment_39074

Let's keep this discussion in one thread instead of repeating it here: reinstalling l4 <http://community.logos.com/forums/t/5042.aspx> (I know it's hard to find these here).

I'm certainly not a Logos tech, (just a forum rat) but I did read through your Logs, I'm only guessing but it looks like you're logs are truncated. This can be from clicking the the OK, or Done button too early.

Go ahead and let it crash again, this time see if you can let the error dialog sit for - oh, let's say a minute - to give the logger time to finish writting out the error. Then could you post another log file?

I believe this is going to be one for the Logos Techs. I know they read these threads, all the more reason to keep it all in one place.

Thanks,

EDIT: I just looked at your earlier log and it's truncated in the exact same place. Running it longer may not make a difference after all.

TCBlack

https://community.logos.com/discussion/comment/39789#Comment_39789

Again, I'm not a programmer so this is guesswork after googling around a bit. It almost sounds like a bad install of the NET framework. Try repairing .NET Framework 3.5 SP 1 from Add/Remove Programs, or uninstall and reinstall.

If you need a .net reinstall link: http://www.microsoft.com/downloads/details.aspx?FamilyId=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en

TCBlack

https://community.logos.com/discussion/comment/39793#Comment_39793

OK, one more suggestion: more of a wild hair idea really. But if the .NET reinstall fails you can try turning off the logging: Diagnostic Logging

Just look at that link and set the Dword to 0 instead of to 1 (or use the script to turn it off).

Howard Silverman

https://community.logos.com/discussion/comment/39795#Comment_39795

i reinstalled the net framework 3.5 sp1 but that did not help. i sent the log to a tech person whom i spoke with last night - who was very helpful. then i installed the program Visual Studio 2010 beta 2. it is a big program and it took a long time - but it seems to have done the trick. it has the jit debugger. (i had tried to install it earlier in the day but it failed) but the quetion is why would i get this application error in the first place. Hopefully there will be a patch for it so i can at some point uninstall visual studio which i have no need for.

thanks,

howard

TCBlack

https://community.logos.com/discussion/comment/39913#Comment_39913

Glad it's "solved" well, more like kludged Howard. You're the only individual I've seen on the forums report this but I sure hope they can find something in your logs to fix it for good.

Howard Silverman

https://community.logos.com/discussion/comment/39920#Comment_39920

well, of course now it has crashed again. here was the error message from visual studio:

“The following module was built with either optimizations enabled or without debug information:

C:\documents and settings\HOWARD\local settings\application data\logos 4\system\logos 4.exe

To debug this module, change its project build configuration to Debug mode.”

as they say in the old country OY VEY.

thanks,

howard

TCBlack

https://community.logos.com/discussion/comment/39943#Comment_39943

Howard,

You poor man. I feel for you brother! Um... what version are you running? Check HELP >ABOUT.

Bradley Grainger (Logos)

i keep getting an error message telling me that "no JIT degugger found". L4 then crashes. it usually happens when i am using the passage guide. i tried using several differetn registry cleaners but it keeps coming back. has anyone else had this problem?

Hi Howard,

The fundamental problem here is that Logos 4 has encountered an unexpected error, and can't continue. Normally, the program would just crash (and offer to send the error report to Microsoft). If you are a software developer, you can choose to debug the program when it crashes (to try to figure out what went wrong); most users don't need (or want!) to do this. The "no JIT debugger" message makes it sound like Windows thinks that you do want to debug the program, but when it looks for a debugger, it can't find one. This is probably some kind of configuration error in Windows, but really unrelated to the underlying problem. (As other posters have noted, you can choose to install a debugger, which will suppress this message from Windows. However, it won't fix the bug in Logos 4.)

Your log files show a crash we have never seen before; searching for the error message on the Internet isn't returning a lot of useful information either (unfortunately). Can you please provide some more information about your system that might help us understand this error? What OS are you running? How many monitors do you have? What screen resolution(s)? Are you using high DPI or "large fonts"? What is your video card manufacturer?

Matthew C Jones

https://community.logos.com/discussion/comment/39793#Comment_39793

Again, I'm not a programmer so this is guesswork after googling around a bit. It almost sounds like a bad install of the NET framework. Try repairing .NET Framework 3.5 SP 1 from Add/Remove Programs, or uninstall and reinstall.

I have not had any problem running Logos 4 with Vista. But I did have a similar (not exact) problem running another program under XP SP3. I read somewhere on Microsoft's site to uninstall previous NET Framework versions after installing the latest. I don't remember the rationale but I did it and it solved that problem.

This might be totally unrelated to what Howard is experiencing. It just sounds similar to me.

Howard Silverman

https://community.logos.com/discussion/comment/40998#Comment_40998

thank you very much for an excellent explanation.

here is the information that you requested:

OS: Windows XP professional 2002 sp3

display: multiple monitors* on NVIDIA Quadro FX 2500M

screen resolution: 1440 x 900

i am using 120 dpi large fonts

my computer is a Dell Precision M90

* i ususally use L4 at my office where i use an Acer monitor with the information that i gave you. i also use L4 at home where i only use the laptop monitor. the problem occurs on both.

i hope you can help!

thank you

howard silverman