Class HostDebugStoppedParams
- Namespace
- RDCore.SDK.Platform.Components
- Assembly
- RDCore.SDK.dll
Request for rdcore/host/debug/stopped, from the environment host to the language server: the handler of an event stopped while no program runs, and
waits there if a client takes the stop.
[Method("rdcore/host/debug/stopped", Direction.ServerToClient)]
public record HostDebugStoppedParams : IRequest, IRequest<Unit>, IRequest<HostDebugStoppedResult>, IBaseRequest, IEquatable<HostDebugStoppedParams>
- Inheritance
-
HostDebugStoppedParams
- Implements
-
IRequestIRequest<Unit>IRequest<HostDebugStoppedResult>IBaseRequest
- 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. A stop in its
handler (a Stop, a breakpoint, a failed Debug.Assert, an error a debugger waits at) has no request to answer
Suspended to, since no request runs the handler. The host asks this instead, on the thread that stopped, and serves the calls
asked of that thread while it waits for the answer.
The language server answers Taken when its client expects the SessionStops capability, and tells it
(rdcore/session/debug/stopped): the handler then waits as a program waits at a stop, and rdcore/host/debug/* act on it. Otherwise the handler
does not wait: it is unwound, and the session goes on with no program running, as with no debugger.
Part of the component protocol (RDCoreComponentProtocol), outside the SDK's compatibility promise.
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; }