DkmRuntimeInstance.OwnsCurrentExecutionLocation Method
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.
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.
Location constraint: API must be called from a Monitor component (component level < 100,000).
public:
bool OwnsCurrentExecutionLocation(Microsoft::VisualStudio::Debugger::Stepping::DkmStepper ^ Stepper, Microsoft::VisualStudio::Debugger::Stepping::DkmStepArbitrationReason Reason);public bool OwnsCurrentExecutionLocation(Microsoft.VisualStudio.Debugger.Stepping.DkmStepper Stepper, Microsoft.VisualStudio.Debugger.Stepping.DkmStepArbitrationReason Reason);member this.OwnsCurrentExecutionLocation : Microsoft.VisualStudio.Debugger.Stepping.DkmStepper * Microsoft.VisualStudio.Debugger.Stepping.DkmStepArbitrationReason -> boolPublic Function OwnsCurrentExecutionLocation (Stepper As DkmStepper, Reason As DkmStepArbitrationReason) As Boolean- Stepper
- DkmStepper
[In] DkmStepper represents a request to step a thread. It facilitates shared object lifetime between the various runtime debug monitors that participate in stepping.
- Reason
- DkmStepArbitrationReason
[In] DkmStepArbitrationReason the reason step arbitration is occurring.
[Out] If the runtime instance wants control of the step, it should set this to true. It should be set to false to not take control.
| Produkt | Wersje |
|---|---|
| Visual Studio SDK | 2015, 2017, 2019, 2022 |