You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(gdb): start the gdb server when restoring from a snapshot
Upstream wires gdb only into the boot path; restored microVMs never
started the gdb server. Accept a gdb_socket_path restore-time override
on the load-snapshot request (alongside network_overrides and
clock_realtime) and wire attach_debug_info + gdb_thread into
build_microvm_from_snapshot (x86_64), arming the entry breakpoint at the
restored vCPU RIP so gdb takes control at the resume point.
Carrying the socket on LoadSnapshotParams keeps it a pure restore-time
knob: no machine-config update is needed before the load (which would
forbid the snapshot load), and there is no boot-time value to preserve
across restore. persist sets the restored machine config's
gdb_socket_path from the load param, which the snapshot builder reads.
Also add resolve_gdb_socket_path() with a FIRECRACKER_GDB_SOCKET env
fallback, so launchers that cannot set the load request can still enable
gdb.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Nikita Kalyazin <nikita.kalyazin@e2b.dev>
0 commit comments