dbg — Debug & Profiling CLI

What it does

dbg provides a canonical, persistent command-line debugging and profiling interface that unifies backends (lldb, netcoredbg, perf, callgrind, etc.) and records breakpoint hits and traces into a session DB. It supports flow control (run/step/continue), breakpoints, inspection, disassembly, hit capture, diffing sessions, replay, and GPU-specific profiling via a separate gdbg binary. The skill documents adapter-based preconditions and a vocabulary that maps user goals to the correct backend.

When to use it

Use dbg when you need deterministic runtime inspection or profiling instead of guessing from source: debugging live processes, attaching to PIDs, profiling hotspots, collecting JIT disassembly, comparing runs, or investigating memory errors and GPU kernel performance. Prefer gdbg for GPU workloads and adapters for backend-specific prechecks.

What's included

• Scripts: none detected; the skill references an adapters/ directory with backend-specific guidance and canonical command translations.
• References: adapters/_canonical-commands.md and adapters/_taxonomy-debug.md are required reading for backend mappings and question-driven workflows.
• Instructions: how to start sessions, attach, capture hits, diff runs, manage session lifecycle, and safety notes about sandboxing and invalid targets.

Compatible agents

Inferred compatibility: language- and runtime-aware agents that can orchestrate system tools and interpret debugger output (systems-level assistants, devops debuggers, and advanced code agents).