Jul 07, 2017 dev c debug, dev c debug not working, dev c debug watch variable, dev c debugger, dev c debugger not working. Yes that's true same message i also received while trying to debug my project, even after selecting yes in enable debbuging and rebuild project, i solve it in this way may be it will help you, goto menu project-project option, select tab compiler, select item linker in left panel and then finally select 'Generate debugging info to yes' in. Enable Debugging Mode with and without Login on Windows 10. Some users would like to know how to enable debugging after logging in Windows 10 computer, while others may wonder how to enable it if failed to log on the computer. Therefore, this article respectively illustrates how to enable debugging mode with and without login.
-->When a kernel debugging connection is established, the system gives a kernel debugger control over its execution. Also, when a bug check occurs or a kernel-mode program communicates with a debugger, the computer waits for a response from a kernel debugger before it continues.
There are four basic debugging methods that you can configure by using boot parameters:
- Single-computer (local) debugging
- Debugging with a null-modem cable
- Debugging with an IEEE 1394 cable (only if the target computer and the host computer are both running Microsoft Windows 7 or a later version of Windows)
- Debugging with a USB 2.0 debug cable (only if the target computer and the host computer are both running Microsoft Windows 7 or a later version of Windows)
Boot Option for Local Debugging in Windows
To enable kernel debugging on a single computer, use the BCDEdit /debug boot option.
To use BCDEdit, open a Command Prompt window with elevated privileges (right-click Command Prompt and click Run as administrator from the shortcut menu).
The /debug option has the following syntax:
The {ID} is the ID that is associated with the boot entry, such as {DEFAULT} for the default OS boot entry. If you do not specify an {ID}, the command modifies the operating system that is currently active. For more information about working with boot entry identifiers, see Boot Options Identifiers.
The following command enables kernel debugging for the current Windows operating system boot entry:
You can use the bcdedit /enum command to view the current boot entries and their settings.
For more details, see BCDEdit /debug.
Boot Options to Debug with a Null-Modem Cable in Windows
To enable debugging with a null-modem cable in Windows, use BCDEdit and set the debugging connection type to 'SERIAL'. You can set this globally by using the BCDEdit /dbgsettings command followed by serial, or set it for a specific boot entry by using the BCDEdit /set command followed by debugtype serial. You must also use the BCDEdit /debug command to enable kernel debugging globally or for the desired operating system.
If BCDEdit has not been used, the default global debug settings are for serial communications, using COM1 and a baud rate of 115,200.
To display the current settings, use the following command:
How To Enable Debugging In Dev-cpp
To use BCDEdit, open a Command Prompt window with elevated privileges (right-click Command Prompt and click Run as administrator from the shortcut menu).
To set the global debug settings to serial communications, use the following syntax:
bcdedit /dbgsettings serial [ debugport:port] [ baudrate:baud]
The following example shows how to specify serial communications as the global debug setting.
To set the debug settings to serial for a specific boot entry, or for the current entry, use the following syntax: Kspectra 3.5 free download for mac.
bcdedit /set [{ID}] debugtype serial
bcdedit /set [{ID}] debugportport
bcdedit /set [{ID}] baudratebaud
If no {ID} is specified, the settings apply to the currently active boot entry.
The following example shows how to specify the serial debug settings for a the default boot entry. To enable the debug settings, you must reboot your computer and select that boot entry you have configured for debugging.
You can use the bcdedit /enum command to view the current boot entries and their settings.
For more details, see BCDEdit /debug and BCDEdit /dbgsettings.
Boot Parameters to Debug with a 1394 Cable in Windows
To enable debugging with an IEEE 1394 cable in Windows, use BCDEdit and set the debugging connection type to '1394'. You can set this globally by using the BCDEdit /dbgsettings command followed by 1394, or set it for a specific boot entry by using the BCDEdit /set command followed by debugtype 1394. You must also use the BCDEdit /debug command to enable kernel debugging globally or for the desired operating system.
To use BCDEdit, open a Command Prompt window with elevated privileges (right-click Command Prompt and click Run as administrator from the shortcut menu).
To set the debug settings for 1394 globally, use the following syntax:
bcdedit /dbgsettings 1394 [ channel:channel ]
The following example shows how to specify 1394 as the global debug setting.
To set the debug settings to 1394 for a specific boot entry, or for the current entry, use the following syntax:
bcdedit /set [{ID}] debugtype 1394
bcdedit /set [{ID}] channelchannel
If an {ID} is not specified, the settings apply to the current boot entry.
The following example shows how to specify the 1394 debug settings for a specific boot entry, and how to use the /debug option to enable kernel debugging for the default boot entry. Note that to enable the debug settings, you must reboot your computer and select the boot entry you have configured for debugging.
You can use the bcdedit /enum command to view the current boot entries and their settings.
For more details, see BCDEdit /debug and BCDEdit /dbgsettings.
Boot Parameters to Debug with a USB 2.0 Debugging Cable in Windows
To enable debugging with a USB cable in these versions of Windows, use BCDEdit and set the debugging connection type to 'USB'. You can set this globally by using the BCDEdit /dbgsettings command followed by usb, or set it for a specific boot entry by using the BCDEdit /set command followed by debugtype usb. You must also use the BCDEdit /debug command to enable kernel debugging globally or for the desired operating system.
To use BCDEdit, open a Command Prompt window with elevated privileges (right-click Command Prompt and click Run as administrator from the shortcut menu).
To set the debug settings for USB globally, use the following syntax:
bcdedit /dbgsettings usb [targetname:name]
The following example shows how to specify USB as the global debug setting.
To set the debug settings to USB for a specific boot entry, or for the current entry, use the following syntax:
bcdedit /set [{ID}] debugtype usb
bcdedit /set [{ID}] targetnamename]
If no {ID} is specified, the settings apply to the current boot entry.
The following example shows how to specify the USB debug settings for a specific boot entry, and how to use the /debug command to enable kernel debugging for the default boot entry. Note that to enable the debug settings, you must reboot your computer and select the boot entry you have configured for debugging.
You can use the bcdedit /enum command to view the current boot entries and their settings.
For more details, see BCDEdit /debug and BCDEdit /dbgsettings.
Boot Parameters to Debug the Boot Process in Windows
To enable boot debugging, use the BCDEdit /bootdebug command and specify the appropriate boot component. If you wish to perform kernel debugging after Windows starts, use the BCDEdit /debug command as well.
You must also select a debugging connection (serial, 1394, or USB). This can be done with either the BCDEdit /dbgsettings or BCDEdit /set command, just as in normal kernel debugging.
For more details, see BCDEdit /bootdebug.
-->Just-In-Time debugging can launch Visual Studio automatically when an app running outside Visual Studio errors or crashes. With Just-In-Time debugging, you can test apps outside of Visual Studio, and open Visual Studio to begin debugging when a problem occurs.
Just-In-Time debugging works for Windows desktop apps. It does not work for Universal Windows Apps, or for managed code that is hosted in a native application, such as Visualizers.
Tip
If you just want to stop the Just-In-Time Debugger dialog box from appearing, but don't have Visual Studio installed, see Disable the Just-In-Time Debugger. If you once had Visual Studio installed, you may need to disable Just-In-Time debugging from the Windows registry.
Enable or disable Just-In-Time debugging in Visual Studio
Note
To enable or disable Just-In-Time debugging, you must be running Visual Studio as an administrator. Enabling or disabling Just-In-Time debugging sets a registry key, and administrator privileges may be required to change that key. To open Visual Studio as an administrator, right-click the Visual Studio app and choose Run as administrator.
You can configure Just-In-Time debugging from the Visual Studio Tools > Options (or Debug > Options) dialog box.
To enable or disable Just-In-Time debugging:
- On the Tools or Debug menu, select Options > Debugging > Just-In-Time.
- In the Enable Just-In-Time debugging for these types of code box, select the types of code you want Just-In-Time debugging to debug: Managed, Native, and/or Script.
- Select OK.
If you enable the Just-In-Time debugger, but it doesn't open when an app crashes or errors, see Troubleshoot Just-In-Time debugging.
Disable Just-In-Time debugging from the Windows registry
Just-In-Time debugging may still be enabled even if Visual Studio is no longer installed on your computer. If Visual Studio is no longer installed, you can disable Just-In-Time debugging by editing the Windows registry.
To disable Just-In-Time debugging by editing the registry:
How To Enable Debugging
- From the Windows Start menu, run the Registry Editor (regedit.exe).
- In the Registry Editor window, locate and delete the following registry entries:
- HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkDbgManagedDebugger
- HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionAeDebugDebugger
- If your computer is running a 64-bit operating system, also delete the following registry entries:
- HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkDbgManagedDebugger
- HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindows NTCurrentVersionAeDebugDebugger
Make sure not to delete or change any other registry keys. - Close the Registry Editor window.
Enable Just-In-Time debugging of a Windows Form
By default, Windows Form apps have a top-level exception handler that lets the app keep running if it can recover. If a Windows Forms app throws an unhandled exception, it shows the following dialog:
To enable Just-In-Time debugging instead of standard Windows Form error handling, add these settings:
- In the
system.windows.forms
section of the machine.config or <app name>.exe.config file, set thejitDebugging
value totrue
: - In a C++ Windows Form application, also set
DebuggableAttribute
totrue
in a .config file or in your code. If you compile with /Zi and without /Og, the compiler sets this attribute for you. If you want to debug a non-optimized release build, however, you must setDebuggableAttribute
by adding the following line in your app's AssemblyInfo.cpp file:For more information, see DebuggableAttribute.
Use Just-In-Time debugging
This example walks you through Just-In-Time debugging when an app throws an error.
- You must have Visual Studio installed to follow these steps. If you don't have Visual Studio, you can download the free Visual Studio Community Edition.
- Make sure Just-In-Time debugging is enabled in Tools > Options > Debugging > Just-In-Time.
For this example, you'll make a C# console app in Visual Studio that throws a NullReferenceException.
- In Visual Studio, create a C# console app (File > New > Project > Visual C# > Console Application) named ThrowsNullException. For more information about creating projects in Visual Studio, see Walkthrough: Create a simple application.
- When the project opens in Visual Studio, open the Program.cs file. Replace the Main() method with the following code, which prints a line to the console and then throws a NullReferenceException:
- To build the solution, choose either the Debug (default) or Release configuration, and then select Build > Rebuild Solution.Note
- Choose Debug configuration for the full debugging experience.
- If you select Release configuration, you must turn off Just My Code for this procedure to work. Under Tools > Options > Debugging, deselect Enable Just My Code.
For more information about build configurations, see Understanding build configurations. - Open the built app ThrowsNullException.exe in your C# project folder (..ThrowsNullExceptionThrowsNullExceptionbinDebug or ..ThrowsNullExceptionThrowsNullExceptionbinRelease).You should see the following command window:
- The Choose Just-In-Time Debugger dialog opens.Under Available Debuggers, select New instance of <your preferred Visual Studio version/edition>, if not already selected.
- Select OK.The ThrowsNullException project opens in a new instance of Visual Studio, with execution stopped at the line that threw the exception:
You can start debugging at this point. If you were debugging a real app, you would need to find out why the code is throwing the exception.
Caution
If your app contains untrusted code, a security warning dialog box appears, enabling you to decide whether to proceed with debugging. Before you continue debugging, decide whether you trust the code. Did you write the code yourself? If the application is running on a remote machine, do you recognize the name of the process? If the app is running locally, consider the possibility of malicious code running on your computer. If you decide the code is trustworthy, select OK. Otherwise, select Cancel.
Troubleshoot Just-In-Time debugging
https://renewsushi.weebly.com/download-latest-python-mac-stackoverflow.html. If Just-In-Time debugging doesn't start when an app crashes, even though it is enabled in Visual Studio:
- Windows Error Reporting could be taking over the error handling on your computer.To fix this issue, use Registry Editor to add a DWORD Value of Disabled, with Value data of 1, to the following registry keys:
- HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsWindows Error Reporting
- (For 64-bit machines): HKEY_LOCAL_MACHINESoftwareWOW6432NodeMicrosoftWindowsWindows Error Reporting
https://bidsheavenly681.weebly.com/need-for-speed-most-wanted-cheat-code-for-ppsspp.html. For more information, see .WER settings. - A known Windows issue may be causing the Just-In-Time debugger to fail.The fix is to add a DWORD Value of Auto, with Value data of 1, to the following registry keys:
- HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionAeDebug
- (For 64-bit machines): HKEY_LOCAL_MACHINESoftwareWOW6432NodeMicrosoftWindows NTCurrentVersionAeDebug
You might see the following error messages during Just-In-Time debugging:
- Unable to attach to the crashing process. The specified program is not a Windows or MS-DOS program.The debugger tried to attach to a process running under another user.To work around this problem, in Visual Studio, open Debug > Attach to Process, and find the process you want to debug in the Available Processes list. If you do not know the name of the process, find the Process ID in the Visual Studio Just-In-Time Debugger dialog. Select the process in the Available Processes list, and select Attach. Select No to dismiss the Just-In-Time debugger dialog.
- Debugger could not be started because no user is logged on.There is no user logged onto the console, so there is no user session to display the Just-In-Time debugging dialog.To fix this problem, log onto the machine.
- Class not registered.The debugger tried to create a COM class that is not registered, probably due to an installation problem. Fineprint v6.25 incl keymaker-zwt (by load).To fix this problem, use the Visual Studio Installer to reinstall or repair your Visual Studio installation.