go-delve/delve

This system is a Go debugger (Delve) that provides deep inspection of running and crashed processes, supporting native execution, core dumps, and record-and-replay debugging. It features a modular architecture with a headless service layer exposing a JSON-RPC and DAP (Debug Adapter Protocol) API for remote and IDE integration. The debugger handles complex DWARF debug information, multi-architecture register states, and eBPF-based tracing, while offering a scriptable terminal interface for automated workflows.

This period focused on restructuring the debugger into a modular, headless service architecture using Cobra and RPC interfaces, while simultaneously refactoring the DWARF parsing and DWARF expression evaluation logic into dedicated packages. The work also expanded debugging capabilities to include core files, Windows minidumps, and Mozilla rr record-and-replay, supported by extensive integration tests and fixture updates.

35 changes

This period focused on expanding the debugger's integration capabilities by implementing the Debug Adapter Protocol (DAP) for VSCode and introducing Starlark scripting support in the terminal. The work also included significant refactoring of the logging subsystem, consolidation of Linux-specific utilities, and the addition of Windows minidump parsing.

23 changes

This period focused on expanding the debugger's support for new hardware architectures, including ARM64 on Windows, PowerPC, LoongArch64, and RISC-V. It also introduced significant backend improvements, such as an eBPF-based tracing system and a stack-based expression evaluator, while adding debug information retrieval capabilities via debuginfod.

25 changes

This period focused on enhancing debugging capabilities by introducing a new package for detecting debugger attachment and adding test fixtures for dynamic loading and child process spawning. The team also expanded text processing support and updated dependencies, including migrating the YAML library and updating the trie library.

7 changes

go-delve/delve was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.