Skip to content

"CLI-Anything: Making ALL Software Agent-Native" -- CLI-Hub: https://clianything.cc/

Python

chore: sync lldb root skill

aimidi476c68411130
diff --git a/skills/cli-anything-lldb/SKILL.md b/skills/cli-anything-lldb/SKILL.md
index 37927290b..e0604688d 100644
--- a/skills/cli-anything-lldb/SKILL.md
+++ b/skills/cli-anything-lldb/SKILL.md
@@ -1,7 +1,7 @@
---
name: "cli-anything-lldb"
description: Stateful LLDB debugging via LLDB Python API
-version: 0.1.0
+version: 1.0.0
command: cli-anything-lldb
install: pip install cli-anything-lldb
requires:
@@ -28,6 +28,7 @@ Use this CLI to run structured LLDB debugging workflows with JSON output.
- Read/find process memory
- Load core dumps
- Interactive REPL with persistent session state
+- Formal stdio Debug Adapter Protocol server for AI/editor clients
## Quick Commands
@@ -35,13 +36,43 @@ Use this CLI to run structured LLDB debugging workflows with JSON output.
cli-anything-lldb --json target create --exe /path/to/exe
cli-anything-lldb --json process launch --arg foo --arg bar
cli-anything-lldb --json breakpoint set --function main
+cli-anything-lldb --json breakpoint set --function PluginEntry --allow-pending
cli-anything-lldb --json process continue
+cli-anything-lldb --json process interrupt
cli-anything-lldb --json thread backtrace --limit 20
cli-anything-lldb --json frame locals
cli-anything-lldb --json expr "myVar"
cli-anything-lldb --json memory read --address 0x1000 --size 64
+cli-anything-lldb --json session close
```
+## Debug Adapter Protocol
+
+Use the DAP entry point when an AI client needs a real debug adapter lifecycle
+instead of shelling out separate CLI commands:
+
+```bash
+cli-anything-lldb-dap
+```
+
+or:
+
+```bash
+cli-anything-lldb dap
+```
+
+The DAP server speaks stdio `Content-Length` frames and must have exclusive
+stdout. Do not print logs to stdout around it. Supported requests include
+`initialize`, `launch`, `attach`, `configurationDone`, `setBreakpoints`,
+`setFunctionBreakpoints`, `threads`, `stackTrace`, `scopes`, `variables`,
+`setVariable`, `evaluate`, `continue`, `pause`, `next`, `stepIn`, `stepOut`,
+`source`, `loadedSources`, `readMemory`, `modules`, `exceptionInfo`,
+`disassemble`, and `disconnect`.
+
+DAP variables can expose child references for structs/classes/arrays. Use
+`setVariable` only while stopped; LLDB may reject writes to optimized-out or
+read-only values.
+
## Command Groups
### target
@@ -52,10 +83,11 @@ cli-anything-lldb --json target info
### process
```bash
-cli-anything-lldb --json process launch [--arg ARG ...] [--env KEY=VALUE ...] [--cwd DIR]
+cli-anything-lldb --json process launch [--arg ARG ...] [--env KEY=VALUE ...] [--cwd DIR] [--stop-at-entry]
cli-anything-lldb --json process attach --pid 1234
cli-anything-lldb --json process attach --name myapp --wait-for
cli-anything-lldb --json process continue
+cli-anything-lldb --json process interrupt
cli-anything-lldb --json process detach
cli-anything-lldb --json process info
```
@@ -64,6 +96,7 @@ cli-anything-lldb --json process info
```bash
cli-anything-lldb --json breakpoint set --function main
cli-anything-lldb --json breakpoint set --file main.c --line 42 --condition "i > 10"
+cli-anything-lldb --json breakpoint set --function LateLoadedSymbol --allow-pending
cli-anything-lldb --json breakpoint list
cli-anything-lldb --json breakpoint delete --id 1
cli-anything-lldb --json breakpoint enable --id 1
@@ -94,10 +127,12 @@ cli-anything-lldb --json core load --path /path/to/core
## Agent Usage Notes
- Prefer `--json` for all automated flows.
-- Non-REPL commands share state across separate invocations through the persistent session daemon until you run `session close` or the idle timeout expires.
-- Use REPL when you want an interactive long-running debugger session:
- - run `cli-anything-lldb`
- - execute multi-step commands in one session
+- Separate non-REPL invocations share a persistent session daemon by default.
+- Use `--session-file PATH` or `CLI_ANYTHING_LLDB_SESSION_FILE` to pin an explicit session for a task.
+- Run `cli-anything-lldb --json session close` when finished so attached processes detach and launched debuggees are cleaned up.
+- Use REPL when a human-like interactive shell is more convenient, not because persistence requires it.
+- Unresolved CLI breakpoints fail by default; pass `--allow-pending` only when a future module/symbol load is expected.
+- DAP unresolved breakpoints use protocol semantics: `verified: false` until resolved.
- `memory find` uses a chunked scan capped at 1 MiB per call.
- Call `target create` before process or core commands.
- Expect structured errors: `{"error": "...", "type": "..."}`