StackScope

VS Code extension for inspecting debugger-backed memory during a stopped debug session.

What it does

StackScope reads and writes debugger-backed memory through the active debug adapter, presenting it in virtualized hex and decoded view. Memory and registers have separate VS Code views. It also supports address expressions, register sets, memory presets, byte-change tracking, register and memory watchpoints, call-stack navigation, and disassembly navigation.

Requirements

• VS Code version ^1.110.0
• Active, stopped debug session
• Debug adapter supporting DAP readMemory and expression evaluation

Some workflows, including call stack and disassembly, also depend on adapter support for corresponding DAP requests.

Quick start

1. Start debugging and pause execution.
2. Run StackScope: Open Memory View.
3. Enter target such as 0x20000000, $sp, or &myVar.
4. Scroll to load memory pages. Use Settings to change columns, unit size, number format, and total size.
5. Open StackScope: Focus Registers View to inspect registers in its own Activity Bar view.
6. When adapter write support is available, select memory bytes or a register value to edit it. Memory accepts hex, decimal, octal, binary, and ASCII; registers also accept a raw debugger expression.
7. Select a register or memory range watch action while paused. DAP data breakpoints are used first; cppdbg sessions configured with GDB can use the GDB fallback when the adapter does not expose data breakpoints.

Commands

• StackScope: Open Memory View
• StackScope: Focus Memory View
• StackScope: Focus Registers View
• StackScope: Open Memory View (Editor Tab)
• StackScope: Open Call Stack (Editor Tab)
• StackScope: Open Disassembly (Editor Tab)

Development

pnpm install
pnpm run compile

Use Run Extension from .vscode/launch.json for an Extension Development Host.

Documentation

• Getting started
• Architecture
• Protocol and host API
• Development
• Testing
• Known constraints
• Documentation index

Limitations

Memory and register reads require stopped session. Watchpoint availability depends on the active adapter: DAP data breakpoints are preferred, while GDB register fallback requires cppdbg with MIMode: "gdb" and may be limited by hardware watchpoint resources.

License

MIT