| Previous | Next |
| ERROR_WAIT_FOR_OPLOCK | ERROR_DBG_CONTINUE |
ERROR_DBG_EXCEPTION_HANDLED
the debugger reports that it handled the current exception.
ERROR_DBG_EXCEPTION_HANDLED identifies this condition: This debugger continuation result tells Windows that the debugger consumed the exception and execution may continue according to the modified or preserved thread context.
Where the result appears
- WaitForDebugEvent and ContinueDebugEvent loops.
- exception breakpoints.
- debuggers that patch register state or instruction bytes.
- Test harnesses supervising faulting child processes.
What to collect
- debug event code and first-chance flag.
- thread context before and after handling.
- exception address and parameters.
- continuation status passed for the matching process and thread IDs.
Handling and recovery
Return this result only when the debugger has deliberately handled the exception. Ensure the continuation corresponds to the current debug event and that any changed instruction pointer, stack, or registers form a valid execution state.
Common misinterpretation
Marking an unhandled access violation as handled can create an endless fault loop or silent corruption. When the debugger only inspected the event, use the unhandled continuation path.
References
Looking for a different code? Search another status or error code.