LLDB-SERVER(1)

✨ LLDB-SERVER(1) — the lldb-server glow-up ✨

okay bestie, welcome to LLDB-SERVER(1), aka the manual page for lldb-server from the LLDB crew 💖 this is the whole thing, nothing skipped, let's go 🫶

---

🌸 NAME 🌸

lldb-server — LLDB Documentation. that's it, that's the name, iconic 💅

---

🦋 SYNOPSIS 🦋

lldb-server v[ersion]
lldb-server g[dbserver] [options]
lldb-server p[latform] [options]

---

💜 DESCRIPTION 💜

lldb-server is the server counterpart of the LLVM debugger, no cap. The server is the one that runs and monitors the debugged program, while you (the user) vibe with it through a client — either running locally or connecting remotely. it's giving long-distance relationship but make it debugging 😭

All of the code in the LLDB project is available under the Apache 2.0 License with LLVM exceptions. periodt.

---

👑 COMMANDS 👑

The first argument to lldb-server specifies a command to run. main character decision energy.

• v[ersion] — Prints lldb-server version and exits. short and sweet, a little goodbye kiss 💋
• g[dbserver] — Runs the server using the gdb-remote protocol. LLDB can afterwards connect to the server using the gdb-remote command. the classic route, fr fr.
• p[latform] — Runs the platform server. LLDB can afterwards connect to the server using platform select, followed by platform connect. fancy platform girlies rise up 🌈

---

🔥 GDBSERVER COMMAND 🔥

lldb-server g[dbserver] [options] [[host]:port] [[--] program args...]

🌟 CONNECTION 🌟

• host:port — Specifies the hostname and TCP port to listen on. Obligatory unless another listening option is used. If host is empty, localhost will be used. If port is zero, a random port will be selected, and written as specified by --pipe or --named-pipe options. slay, autopick.
• --fd <fd> — Communicate over the given file descriptor instead of sockets. not like other girls (sockets).
• --named-pipe <name> — Write the listening port number to the specified named pipe.
• --pipe <fd> — Write the listening port number to the specified pipe (fd).
• --reverse-connect — Connect to the client instead of passively waiting for a connection. In this case, [host]:port denotes the remote address to connect to. she's making the first move, obsessed 💅

🎀 GENERAL OPTIONS 🎀

• --help — Prints out the usage information and exits. the "what does this button do" option 🫶
• --log-channels <channel1 categories...:channel2 categories...> — Channels to log. A colon-separated list of entries. Each entry starts with a channel followed by a space-separated</...> list of categories.
• --log-file <file> — Destination file to log to. If empty, log to stderr.
• --setsid — Run lldb-server in a new session. new session, new me ✨

🌈 TARGET SELECTION 🌈

• --attach <pid-or-name> — Attach to the process given by a (numeric) process id or a name.
• -- program args — Launch a program for debugging.

If neither of target options are used, lldb-server is started without a specific target. It can be afterwards instructed by the client to launch or attach. indecisive queen energy, and we respect it 💖

---

🧚 PLATFORM COMMAND 🧚

lldb-server p[latform] [options] --server --listen [[host]:port]

🌸 CONNECTION 🌸

• --server — Run in server mode, handling multiple connections. If this is not specified, lldb-server will accept only one connection and exit when it is finished. one-and-done vs. social butterfly, pick your vibe.
• --listen <host>:<port> — Hostname and port to listen on. Obligatory. If port is zero, a random port will be used.
• --socket-file <path> — Write the listening socket port number to the specified file.

💜 GENERAL OPTIONS 💜

• --log-channels <channel1 categories...:channel2 categories...> — Channels to log. A colon-separated list of entries. Each entry starts with a channel followed by a space-separated</...> list of categories.
• --log-file <file> — Destination file to log to. If empty, log to stderr.

🦋 GDB-SERVER CONNECTIONS 🦋

• --gdbserver-port <port> — Define a port to be used for gdb-server connections. This port is used for multiple connections.

---

⭐ EXAMPLES ⭐

The server can be started in several modes. choose your fighter 🎮

In order to launch a new process inside the debugger, pass the path to it and the arguments to the debugged executable as positional arguments. To disambiguate between arguments passed to lldb and arguments passed to the debugged executable, arguments starting with a - must be passed after --. The server will launch the new executable and stop it immediately, waiting for the client to connect.

lldb-server g :1234 /path/to/program program-argument --
--program-option

For convenience, passing the executable after -- is also supported.

lldb-server g :1234 -- /path/to/program program-argument
--program-option

In order to attach to a running process, pass --attach along with the process identifier or name. The process will be stopped immediately after starting the server.

note bestie: terminating the server will usually cause the process to be detached and continue execution. she'll keep going without you 😭

lldb-server g :1234 --attach 12345
lldb-server g :1234 --attach program-name

Use gdb-remote command to connect to the server:

(lldb) gdb-remote 1234

lldb-server can also be started without an inferior. In this case, the client can select the target after connecting to the server.

heads up: some commands (e.g. target create) will disconnect and launch a local lldb-server instead. plot twist 🙈

lldb-server g :1234

(lldb) gdb-remote 1234
(lldb) process launch a.out

---

🌈 SEE ALSO 🌈

The LLDB project page https://lldb.llvm.org has many different resources for lldb-server users. go read, bestie, iykyk 📚

---

💖 AUTHOR 💖

LLVM project 👑

---

🎀 COPYRIGHT 🎀

2007-2025, The LLDB Team 💜

---

and that's a wrap on LLDB-SERVER(1) from the LLDB manual, dated Sep 03, 2025 (page 20, for the record-keepers 🫶). stan a debugger server. bye bestie, go debug something gorgeous 💅✨🦋