Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How and where to enable JIT Debugging?

Status
Not open for further replies.

eponymous

ISP
Jul 22, 2004
92
0
0
GB
XP Professional Version 5.1.2600 Service Pack 3 Build 2600

I received the following instruction after an unhandled exception after loading skype mp3 recorder

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

*****************************************

Can you please break the instruction down into a simple step-by-step approach for the absolute newbie which shows precisely which bit of the code is entered at which precise point within machine.config?

a) for instance the <configuration></configuration> tags already exist, so does this mean is is only <system.windows.forms jitDebugging="true" /> that needs to be entered?
b) if so where and how ... for instance system.windows.forms is entered as a "section name" within the <configSections></configSections> tags?
c) this is how system.windows.forms is entered as a section name within the <configSections></configSections> tags:

<section name="system.windows.forms" type="System.Windows.Forms.WindowsFormsSection, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

... is this where I enter <system.windows.forms jitDebugging="true" /> and, if so, could you please kindly re-write the system.windows.forms section (above) so I can see exactly how it is done (as I do not know the protocols i.e. whether to divide by commas or not ... or in what sequence to enter the additional code etc etc)?

This should also help a number of other newbies like me who haven't known where to begin in order to enable jit debugging; when the key fundamental steps are assumed known and then missing as a result. Many thanks.

Seasons Greetings,

Best wishes,
Eponymous
 
Why would you want to debug an application? That's something for the developers to do, not an end-user.

Perhaps you can explain what you are hoping to achieve.
 
Strongm - thanks!

1) skype mp3 recorder fails to initialise and load.
2) instead their is a Microsoft.Net prompt that highlights the error
3) the prompt has 2 options:

a) details of error + action
b) continue (ignore Microsoft.Net prompt and manually load
skype mp3 recorder

a) Details of error + action

It is on clicking this button that I received the following instruction to enable JIT debugging after an unhandled exception after loading skype mp3 recorder [at the end of the details section].

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

*****************************************


In the light of this can you please confirm the precise protocol for including system.windows.forms jitDebugging="true" / in the section name="system.windows.forms" tab of machine.config?

Many thanks,
Eponymous
 
Have you tried updating the .net framework? It looks like the program hasn't been updated since 2009, Does it even work with the new skype version? Are there any errors in the system logs as to the application crashing, and what may be the cause? Did you make sure skype extras manager installed, it doesn't by default anymore.
 
>In the light of this

I'll repeat: as an end-user you are NOT expected to do any debugging. This error message is normally only for use by the developers (who will have a JIT debugger installed as part of Visual Studio, for example) and should not really appear in a released product.


 
See if you can isolate a possible third party program or service as the cause of any error.

310353 - How to Perform a Clean Boot in Windows XP

316434 - HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP

310560 - How to Troubleshoot By Using the Msconfig Utility in Windows XP
 
The error is in the Skype recorder. Get a later version or contact the author.

I'd anticiapte that in the debug code you are seeing something like the following in the details section:

System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {830690FC-BF2F-47A6-AC2D-330BCB402664} failed due to the following error: 80040154.

The error is not with .NET, the error is with the Recorder's COM component not installing properly. I seem to recall there was a bugged version 1.8.3 or 1.8.4 that did exactly what you are describing. Later releases fixed it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top