IDebugEngine3

Applies to: yesVisual Studio noVisual Studio for Mac

Note

This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here

Represents a single debug engine (DE) that controls the debugging of one or more modules.

Syntax

IDebugEngine3 : IDebugEngine2

Notes for Implementers

This interface is implemented by a custom DE (if it supports symbols) to enable the JustMyCode state. This interface must be implemented by the DE if it supports symbols and JustMyCode.

Notes for Callers

This interface is called by the session debug manager (SDM) to pass on user options for locations from which to load symbols. It is also called to set the GUID of the engine when it is instantiated (this GUID is based on the metrics from the time of engine registration). The SDM also calls this interface to set the JustMyCode state and to set all exceptions known by the debugger to a specified state.

Methods in Vtable Order

In addition to the methods inherited from IDebugEngine2, the IDebugEngine3 interface exposes the following methods.

Method Description
SetSymbolPath Sets the path or paths that the DE will use to search for debugging symbols.
LoadSymbols Loads the symbols for all modules that have not yet had their symbols loaded.
SetJustMyCodeState Tells the DE about the JustMyCode information.
SetEngineGuid Sets the DE GUID from the metrics.
SetAllExceptions Set all exceptions currently outstanding to a specified state.

Requirements

Header: msdbg.h

Namespace: Microsoft.VisualStudio.Debugger.Interop

Assembly: Microsoft.VisualStudio.Debugger.Interop.dll

See also