| Previous | Next |
| DBG_TERMINATE_PROCESS | DBG_PRINTEXCEPTION_C |
DBG_CONTROL_C
Ctrl+C was delivered through the debugging path
When a console process is being debugged, Ctrl+C can be reported to the debugger as a debug exception rather than being handled immediately by the target console control handler. The debugger decides whether to consume the event or allow normal exception and console-control processing to continue.
This status is not evidence that the user necessarily intended to terminate the process. Ctrl+C may be used by a debugger as an interrupt command, generated by another console process, or delivered to a console process group.
What to inspect
- Record the console process group and which process generated the control event.
- Check whether the debugger uses Ctrl+C as its own break-in command.
- Decide whether the target should receive its registered console control handler.
- Distinguish Ctrl+C from Ctrl+Break, because applications and debuggers can handle them differently.
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.