| Previous | Next |
| DBG_EXCEPTION_HANDLED | STATUS_FLT_IO_COMPLETE |
DBG_CONTINUE
Execution is being resumed after a debug event
DBG_CONTINUE is used by a debugger when it has finished processing an event returned by WaitForDebugEvent. For an exception event, this continuation value also marks the exception as handled. For process, thread, DLL, and output-debug-string events, it simply acknowledges the event and allows the debuggee to proceed.
The process and thread identifiers passed to ContinueDebugEvent must identify the event that is currently outstanding. Continuing the wrong event or continuing twice indicates a broken debugger state machine rather than a target-process error.
What to inspect
- Match the continuation to the exact process ID and thread ID received with the event.
- Close event-owned file handles at the documented point before continuing create-process or load-DLL events.
- For exceptions, decide explicitly between DBG_CONTINUE and DBG_EXCEPTION_NOT_HANDLED.
- Keep one outstanding event per debug loop and log every transition when diagnosing lost or frozen debuggees.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: ContinueDebugEvent
- Microsoft: WaitForDebugEvent
- Microsoft: writing the debugger main loop
Looking for a different code? Search another status or error code.