ICorDebug Interface
Provides methods that allow developers to debug applications in the common language runtime (CLR) environment.
Note
Mixed-mode (managed and native code) debugging is not supported on Windows 95, Windows 98, or Windows ME, or on non-x86 platforms (such as IA64 and AMD64).
Methods
Method |
Description |
|---|---|
Determines whether launching a new process or attaching to the given process is possible within the context of the current machine and runtime configuration. |
|
Launches a process and its primary thread under the control of the debugger. |
|
Attaches the debugger to an existing process. |
|
Gets an enumerator for the processes that are being debugged. |
|
Returns the ICorDebugProcess object with the given process ID. |
|
Initializes the ICorDebug object. |
|
Specifies the event handler object for managed events. |
|
Specifies the event handler object for unmanaged events. |
|
Terminates the ICorDebug object. |
Remarks
ICorDebug represents an event processing loop for a debugger process. The debugger must wait for the ICorDebugManagedCallback::ExitProcess callback from all processes being debugged before releasing this interface.
The ICorDebug object is the initial object to control all further managed debugging. In the .NET Framework versions 1.0 and 1.1, this object was a CoClass object created from COM. In the .NET Framework version 2.0, this object is no longer a CoClass object. It must be created by the CreateDebuggingInterfaceFromVersion function, which is more version-aware. This new creation function enables clients to get a specific implementation of ICorDebug, which also emulates a specific version of the debugging API.
Note
This interface does not support being called remotely, either cross-machine or cross-process.
Requirements
Platforms: See .NET Framework System Requirements.
Header: CorDebug.idl, CorDebug.h
Library: CorGuids.lib
.NET Framework Versions: 4, 3.5 SP1, 3.5, 3.0 SP1, 3.0, 2.0 SP1, 2.0, 1.1, 1.0