| Previous | Next |
| ERROR_DBG_EXCEPTION_HANDLED | ERROR_CALLBACK_POP_STACK |
ERROR_DBG_CONTINUE
the debugger authorizes execution to continue after the current debug event.
ERROR_DBG_CONTINUE identifies this condition: This is a debugger-control result used to resume a debuggee after processing an event. Unlike exception-specific decisions, it commonly represents ordinary continuation after create-process, load-DLL, output-debug-string, or similar notifications.
Where the result appears
- debug event loops.
- process and thread creation notifications.
- DLL load/unload tracking.
- debugger-driven single-step workflows.
What to collect
- event sequence number and event type.
- process and thread IDs.
- pending breakpoint or single-step state.
- exact continuation code supplied to ContinueDebugEvent.
Handling and recovery
Continue each event exactly once and keep per-thread debugger state synchronized with the event being released. Close event-provided handles when the API contract transfers that responsibility.
Common misinterpretation
The name does not mean every exception should be swallowed. Exception events still require a conscious handled-versus-not-handled decision.
References
Looking for a different code? Search another status or error code.