Expand description
largo dap — the LOGOS debugger served over the Debug Adapter Protocol.
DAP is JSON over stdio with Content-Length framing (like LSP). The entire
protocol lives in the pure DapServer::handle transition — one request
object in, a response plus any events back — so every conformance test drives
it in-process (dap_lock); cmd_dap is only the stdio shell around it.
The server is a thin serializer over
logicaffeine_compile::debug_session::DebugSession — the SAME facade the
Studio drawer renders (session_parity_lock proves they agree), so an editor
stepping through LOGOS over DAP and the in-browser drawer observe one truth.
The headline is real reverse execution: supportsStepBack is advertised and
stepBack/reverseContinue are honest time-travel (the debugger keeps the
whole snapshot history), not a re-run illusion.
Structs§
- DapServer
- The DAP server state machine: an optional live session and a monotone output
sequence counter (DAP stamps every message the adapter sends with a
seq).
Functions§
- cmd_dap
largo dap— speak DAP over stdio withContent-Lengthframing until the peer disconnects. Stdout carries nothing but framed DAP messages.