Just-In-Time Debugging
This topic applies to:
| Visual Studio Edition | Visual Basic | C# | C++ | J# |
| Express | No | No | No | No |
| Standard | Yes | Yes | Yes | Yes |
| Pro/Team | Yes | Yes | Yes | Yes |
Just-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.
If an error occurs while Just-In-Time debugging is enabled, a dialog box opens, asking if you want to debug the program and which debugger you want to use.
If a program running as another user hits a fatal error, a security warning dialog box appears before the debugger starts. For more information, see Security Warning: Attaching to an Untrusted Process Can Be Dangerous.
You can enable Just-In-Time debugging from the Options dialog box. For more information, see How to: Enable/Disable Just-In-Time Debugging.
For Windows forms, you must also enable Just-In-Time debugging in the machine.config or application.exe.config file. For more information, see How to: Enable Just-In-Time Debugging for Windows Forms.
After Visual Studio is installed on a server, the default behavior when an unhandled exception occurs is to show an Exception dialog that requires user intervention to either start Just-In-Time debugging or ignore the exception. This may be undesirable for unattended operation. To configure the server to no longer show a dialog when an unhandled exception occurs (the default behavior prior to installing Visual Studio), use the registry editor to delete the following registry keys:
-
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
-
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
On a 64-bit operating system also delete the following registry keys:
-
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
-
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger
 Note |
|---|
| Just-In-Time debugging will not work for managed code hosted in a native application, such as Visualizers. |
| Note |
|---|
| After installing the .NET Framework on Windows Server 2003 or on Windows 2000 SP3 (or later), Just-In-Time debugging will not work on a process running in a limited user account in a Terminal Services session until the computer has been rebooted. |
See Also
when i play game in my pc after few second my pc show a massage
visual studio just in time debugger
an unhendled win 32 excaption occured in speed exe [3896] eJust-In-Time Debugging xception failed with the following error:No installed debugger has Just-In-Time Debugging enabled in visual studio. Just-In-Time Debugging can be enabled from tools/option/debugging/ Just-In-Time Debugging check the documentation index for Just-In-Time Debugging errors for information..
so what i do???????????
plz help me!!!!!!!!
[tfl - 02 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
- 4/26/2011
- jitukumar1987
- 4/2/2012
- Thomas Lee
I checked the registry keys in http://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx and none of them exist
Visual Studio is not installed on the machine and the app uses .Net framework 4. I want the the process to end by itself without any user intereaction where it is handled to restart itself without waiting for a button press from the user.
There is no jitDebugging secion in the app.config for the exe file for the process. In fact the configuration section of the app.config is empty.
Data Execution Prevention is turned on in the performance options of the system properties.
Thank you.
[tfl - 02 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
- 9/20/2011
- Michael Grounds
- 4/2/2012
- Thomas Lee
[tfl - 02 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
- 12/17/2011
- guappo1
- 4/2/2012
- Thomas Lee
