Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This function unblocks the debuggee thread identified by the given thread identifier.

Syntax

BOOL ContinueDebugEvent(
  DWORD 
dwProcessId,
  DWORD 
dwThreadId,
  DWORD 
dwContinueStatus
);

Parameters

dwProcessId

[in]Specifies the identifier for the process to continue.

dwThreadId

[in] Specifies the thread identifier of the thread to continue.

The combination of process identifier and thread identifier must identify a thread that has previously reported a debugging event.

dwContinueStatus

[in] Specifies how to continue the thread that reported the debugging event.

If the DBG_CONTINUE flag is specified for this parameter and the thread specified by the dwThreadIdparameter previously reported an EXCEPTION_DEBUG_EVENT debugging event, the function stops all exception processing and continues the thread.

For any other debugging event, this flag continues the thread.

If the DBG_EXCEPTION_NOT_HANDLED flag is specified for this parameter and the thread specified by dwThreadIdpreviously reported an EXCEPTION_DEBUG_EVENT debugging event, the function continues exception processing.

If this is a first-chance exception event, the search and dispatch logic of the structured exception handler is used; otherwise, the process is terminated.

For any other debugging event, this flag continues the thread.

Return Value

Nonzero indicates success.

Zero indicates failure.

To get extended error information, call GetLastError.

Remarks

Only the thread that created dwProcessIdwith the CreateProcessfunction can call ContinueDebugEvent.

After ContinueDebugEventsucceeds, the specified thread continues.

Depending on the debugging event previously reported by the thread, different actions occur:

  • If the continued thread previously reported an EXIT_THREAD_DEBUG_EVENT debugging event, ContinueDebugEventcloses the handle the debugger has to the thread.

  • If the continued thread previously reported an EXIT_PROCESS_DEBUG_EVENT debugging event, ContinueDebugEventcloses the handles the debugger has to the process and to the thread.

This call translates to writing the continue status as an event data and setting the debuggee event within the target thread identified by dwThreadId.

Requirements

Header winbase.h
Library coredll.lib
Windows Embedded CE Windows CE 2.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

Reference

CreateProcess