IDkmRuntimeStepper Interface
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
IDkmRuntimeStepper is the interface runtime monitors implement to support stepping.
Implementations of this interface may restrict when they are called using a filter defined in their component configuration. The following properties may be used: BaseDebugMonitorId, EngineId, RuntimeId, TransportKind.
public interface class IDkmRuntimeStepperpublic interface class IDkmRuntimeStepper__interface IDkmRuntimeStepperpublic interface IDkmRuntimeSteppertype IDkmRuntimeStepper = interfacePublic Interface IDkmRuntimeStepperMethods
| AfterSteppingArbitration(DkmRuntimeInstance, DkmStepper, DkmStepArbitrationReason, DkmRuntimeInstance) |
AfterSteppingArbitration is called by the stepping manager on the old controlling runtime instance after stepping arbitration is complete but before the next runtime instance starts stepping. This allows runtimes to clear any stepping state if another runtime took control. If no other runtime monitor claimed the current location, the original monitor should finish the step. This is indicated by NewControllingRuntimeInstance being null. For instance, a runtime instance may choose to step back out if a step-in landed in a location without symbols and no other runtime took control. |
| BeforeEnableNewStepper(DkmRuntimeInstance, DkmStepper) |
BeforeEnableNewStepper is called by the stepping manager before a new stepper is enabled. This gives runtimes the ability to do any initialization that might be required such as performing pre-step function evaluations. |
| NotifyStepComplete(DkmRuntimeInstance, DkmStepper) |
NotifyStepComplete is called by the stepping manager on all non-controlling runtime instances when a step is complete. |
| OnNewControllingRuntimeInstance(DkmRuntimeInstance, DkmStepper, DkmStepArbitrationReason, DkmRuntimeInstance) |
OnNewControllingRuntimeInstance is called by the stepping manager on all non-controlling runtime instances after step arbitration has selected a new controlling runtime instance. |
| OwnsCurrentExecutionLocation(DkmRuntimeInstance, DkmStepper, DkmStepArbitrationReason) |
OwnsCurrentExecutionLocation is called by the stepping manager while it is searching for monitors to perform a step. If the current location in the debuggee is understood by this monitor it can return true here to take control of the step. |
| Step(DkmRuntimeInstance, DkmStepper, DkmStepArbitrationReason) |
Step is called by the stepping manager after it determines this monitor is the correct monitor to perform the step. |
| StepControlRequested(DkmRuntimeInstance, DkmStepper, DkmStepArbitrationReason, DkmRuntimeInstance) |
StepControlRequested is called by the stepping manager when a non-controlling runtime instance detects that the thread has hit a transition into its runtime. If the current controlling runtime instance can stop stepping, it should set Granted to true. Actual control is not given until the requesting runtime calls DkmStepper.TakeStepControl. This two part process allows callers to request control of multiple steppers at the same time. |
| StopStep(DkmRuntimeInstance, DkmStepper) |
StopStep is called by the stepping manager when the process is being continued to clear out any remaining stepping state for a stepper. |
| TakeStepControl(DkmRuntimeInstance, DkmStepper, Boolean, DkmStepArbitrationReason, DkmRuntimeInstance) |
TakeStepControl is called by the stepping manager when a non-controlling runtime instance detects that the thread has hit a transition into its runtime. The stepping manager will forward the call to the current controlling runtime instance. The runtime instance requesting control should first call StepControlRequested on all steppers it wants control of. If they all set Granted to true, the runtime instance should then call this method on each stepper it is taking control of. |