Struct DapExecutor 

pub struct DapExecutor { /* private fields */ }

A [ProgramExecutor] that starts a DAP TCP server and steps through the program interactively.

When used with TransactionExecutor, instead of running to completion, execute() binds a TCP listener and waits for a DAP client (e.g. VS Code) to connect. The client then controls execution via standard DAP commands (continue, step, breakpoints, inspect stack/memory).

Implementations

impl DapExecutor

pub fn new( stack_inputs: StackInputs, advice_inputs: AdviceInputs, options: ExecutionOptions, ) -> DapExecutor

pub fn record_event_mutations(&mut self) -> EventMutationRecorder

Record the advice mutations produced by each event handler invocation of the wrapped host during execution.

Returns a handle to the shared log. When recording was enabled on the installed DapConfig (see DapConfig::record_event_mutations), this is the same log, so embedders that never see the executor instance read the recording through their config handle instead.

One entry is recorded per on_event invocation, in execution order, including empty mutation sets, so the log can be fed directly into an event replay queue (e.g. Executor::into_debug_with_replay or State::new_for_transaction) to debug the same execution later without access to the original host. The log is cleared automatically whenever the DAP session restarts execution from the beginning, so after execution completes it always describes the final run.

pub fn execute_async<H>( self, program: Arc<Package>, host: &mut H, ) -> impl FutureMaybeSend<Result<ExecutionOutput, ExecutionError>>

where H: Host + Send,

impl DapExecutor

pub fn bind_listener(listen_addr: &str) -> Result<TcpListener, String>

Bind the DAP listen socket, reporting failures (bad address, port in use, …) as errors instead of aborting the process.

pub fn execute_on_listener<H>( self, root_package: Arc<Package>, host: &mut H, listener: TcpListener, ) -> Result<ExecutionOutput, ExecutionError>

where H: Host,

Execute a program using an already-bound listener, accepting one DAP client.

This blocks until the session finishes. The caller owns listener setup and can publish its address before starting execution, including when binding an ephemeral port.