> For the complete documentation index, see [llms.txt](https://docs.tryorchard.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryorchard.dev/cli/driving-a-device/debugger.md).

# debugger: lldb console

Drive the on-device lldb debugger: push `lldb-server` to the device, start it, and attach an interactive console to a process. Every verb takes a sandbox selector (uuid / uuid-prefix / name / tag). These commands use the `shell` capability (full ptrace access), so they need a rootable image. On Cuttlefish, launch a debug sandbox (the `cuttlefish-debug` image).

## Check and control lldb-server

```bash
orchard debugger status  my-debug        # installed / running / port
orchard debugger install my-debug        # push lldb-server (needs root) and start it
orchard debugger start   my-debug
orchard debugger start   my-debug --process com.example.app
```

`status` reports whether `lldb-server` is installed, whether it is running, and its port. `install` pushes the NDK `lldb-server` to the device and starts it. `start` can attach to a process on start with `--process`.

## Interactive console

`console` opens an interactive lldb session attached to the device. Set breakpoints, step, and read memory and registers as usual. Ctrl-D exits.

```bash
orchard debugger console my-debug --process com.example.app
```

The console needs an interactive terminal. For the whole userland-to-kernel flow (frida, lldb, syscalls, kernel gdb) see [Debugging a device, userland to kernel](https://github.com/TheFlash2k/orchard/tree/main/docs/DEBUGGING.md).

Add `--json` to `status`, `install` or `start` for the raw agent response.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tryorchard.dev/cli/driving-a-device/debugger.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.