| Previous | Next |
| DBG_RIPEXCEPTION | DBG_COMMAND_EXCEPTION |
DBG_CONTROL_BREAK
Ctrl+Break interrupted the debuggee
Ctrl+Break is commonly used to interrupt a console process without applying the same default semantics as Ctrl+C. Under a debugger it can arrive as a debug exception, allowing the debugger to stop all relevant execution, inspect state, or pass the event onward.
The event can be intentional, for example a user requesting a debugger break, or external to the application. Treat it as a control event and preserve the stopped thread context before deciding how to continue.
What to inspect
- Confirm whether the debugger maps Ctrl+Break to a user break-in operation.
- Record the thread selected for the debug event and the state of other threads.
- Determine whether the application has a console control handler that should receive the event.
- Avoid confusing the status with a breakpoint instruction or kernel debugger break.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: debugging events
- Microsoft: ContinueDebugEvent
- Wine source: NTSTATUS definitions
Looking for a different code? Search another status or error code.