Table of Contents

Class SessionDebugStoppedParams

Namespace
RDCore.SDK.Platform.Protocol
Assembly
RDCore.SDK.Protocol.dll

Notification rdcore/session/debug/stopped: the language server tells a client that expects the SessionStops capability that the handler of an event stopped while no program runs (a Stop, a breakpoint, a failed Debug.Assert, an error a debugger waits at), and waits where it stopped.

public record SessionDebugStoppedParams : IEquatable<SessionDebugStoppedParams>
Inheritance
SessionDebugStoppedParams
Implements
Derived
Inherited Members

Remarks

An event can be handled when no program runs: a click on a form that the prompt showed, or on a form that a macro left shown when it ended. MS-VBA enters break mode at a stop in such a handler, as it does in a program. No request of the client runs that handler, so there is nothing to answer Suspended to: this notification says it instead.

The handler waits as a program waits at a stop. rdcore/session/debug/stack, .../variables, .../evaluate and .../execute act on it. rdcore/session/debug/resume goes on with it, and is answered when it next waits (Suspended) or returns (Completed). rdcore/session/debug/terminate ends it as an End typed at the prompt does: the handler is unwound, and the session is reset.

Properties

Stop

The stop, as the answer of a request that ran a program which waits there says it: Outcome is Suspended, StackTrace begins with the activation that waits, and the error fields say the error for one a debugger waits at. Output is what the handler printed before it stopped.

public ExecuteResult Stop { get; init; }

Property Value

ExecuteResult