ERROR_DBG_CONTROL_BREAK - 696 (0x2B8)
Debugger received control break.
Updated: Feb 21, 2026
Technical Meaning
The ERROR_DBG_CONTROL_BREAK error code indicates that a debugger has received a control break signal. This typically occurs when the user or another process sends a request to terminate the execution of a program being debugged.
Error Details
This error is specific to debugging scenarios and is not encountered in typical application development or system operations. It is part of the Windows Debugging API, which provides mechanisms for developers and administrators to interact with running processes during debugging sessions.
Usage Context
The ERROR_DBG_CONTROL_BREAK code is returned by the operating system when a debugger encounters a control break event. This can happen in various scenarios such as when the user presses Ctrl+C or when another process sends a signal to terminate the debugged program.
Developer Interpretation
When this error is encountered, it signifies that the debugging session has been interrupted due to a control break request. Developers should handle this error by ensuring that their debugging logic can gracefully respond to such interruptions and clean up any resources before terminating the debugged process.
Related Errors
ERROR_DEBUGGER_ATTACHED(107 - 0x6B): Indicates that a debugger has attached to the process.ERROR_DEBUGGER_DETACHING(259 - 0x103): Indicates that a debugger is detaching from the process.
FAQ
Q: What does the ERROR_DBG_CONTROL_BREAK error mean?
A: It indicates that a control break signal has been received by a debugger, typically due to user input or another process terminating the debugged program.
Q: How can I handle this error in my debugging logic?
A: Ensure that your debugging code can properly respond to control break events and clean up any resources before terminating the debugged process.
Summary
The ERROR_DBG_CONTROL_BREAK error is a specific indication of a control break event received by a debugger. It is important for developers to handle this error gracefully in their debugging logic to ensure robustness and reliability during development and testing processes.