# Debugger > Use rust-gdb to inspect variables without modifying code. Prefer this over print debugging when investigating compiler internals or runtime behavior. Use when this capability is needed. - Skill: `tomevault-io/debugger` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/debugger` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/debugger/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/debugger --- # Debugger Debug wado compiler with rust-gdb. ## Usage ```sh cat > /tmp/gdb_commands.txt << 'EOF' file ./target/debug/wado set pagination off break wado-compiler/src/codegen.rs:5985 run compile -o /tmp/out.wasm example/hello.wado info locals print *expr bt 5 quit EOF rust-gdb --batch -x /tmp/gdb_commands.txt ``` ## Common commands | Command | Description | | ------------- | ----------------------------- | | `info locals` | Show local variables | | `print *expr` | Dereference and print pointer | | `bt 5` | Backtrace (top 5 frames) | | `continue` | Resume execution | ## Notes lldb does not work in Claude Code Web due to ptrace restrictions: ``` error: Cannot launch '...': personality get failed: Invalid argument ``` Use rust-gdb instead. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/wado-lang) — claim your Tome and manage your conversions.