DkmBaseDebugMonitorId Class

Definition

Namespace:

Microsoft.VisualStudio.Debugger

Assembly:

Microsoft.VisualStudio.Debugger.Engine.dll

Package:

Microsoft.VisualStudio.Debugger.Engine v17.8.1101801

DkmBaseDebugMonitorId identifies the base debug monitor used to inspect and control the debugged process. For example, DkmBaseDebugMonitorId.WindowsProcess is used for processes debugged by the Win32 debugging API and DkmBaseDebugMonitorId.DumpFile is used for minidumps.

public ref class DkmBaseDebugMonitorId abstract sealed

public ref class DkmBaseDebugMonitorId abstract sealed

class DkmBaseDebugMonitorId abstract sealed

public static class DkmBaseDebugMonitorId

type DkmBaseDebugMonitorId = class

Public Class DkmBaseDebugMonitorId

Inheritance

Object

DkmBaseDebugMonitorId

Properties

ActiveScript	DkmProcess is backed by a live Microsoft Windows ActiveScript process.
ClrVirtualMachine	DkmProcess is debugged using ONLY the ICorDebug API (the process is not being debugging through the Win32 debugging API). This value is used when debugging with the ICorDebug v2 pipeline. Scenarios include debugging a Win32 process running the v2 CLR and debugging a managed process running on a Windows CE device.
DumpFile	DkmProcess is back by a minidump or crashdump file.
DumpFileInterop	Managed/native interop dump debugging.
GpuVirtualMachine	DkmProcess is backed by a live Microsoft Windows D3D process that runs GPU code on GPU hardware or reference rasterizer.
InProcessManagedNativeInterop	DkmProcess is a live win32 process being debugged with the legacy in-process CLR interop model. Both managed and native code can be debugged.
ManagedCoreDumpFile	DkmProcess is backed by a .NET Linux Core Dump file. Such a debuggee can be inspected but all execution control operations are blocked including stepping and func-eval.
ReflectedWin32Process	DkmProcess is backed by a snapshot of a win32 process. Such a debuggee can be inspected but all execution control operations are blocked including stepping and func-eval. This is necessary because the process is not fully initialized and cannot run code.
TimeTravelTrace	DkmProcess is backed by a time travel trace file.
TimeTravelTraceInterop	DkmProcess is backed by a time travel trace file with interop debugging enabled.
WindowsProcess	DkmProcess is backed by a live Microsoft Windows process.