LLDB(1)

✨ lldb 💅

okay so bestie, welcome to the lldb manual page. This is the manual page for lldb 16, and yes it's long, but we're gonna get through it together because honestly? It's giving debugger royalty. 👑

---

🌸 NAME 🌸

lldb — the manual page for lldb 16.

That's it. That's the whole name section. Short, iconic, no notes. 💖

---

🦋 DESCRIPTION 🦋

OVERVIEW: LLDB

USAGE: lldb [options]

so basically you run lldb with some options and it debugs stuff. Iconic behavior. Let's break down every single one, because we do not skip parts in this house. 🫶

🎀 ATTACHING 🎀

• --attach-name <name> — tells the debugger to attach to a process with the given name. Just slide right in. 💅
• --attach-pid <pid> — tells the debugger to attach to a process with the given pid.
• -n <value> — alias for --attach-name
• -p <value> — alias for --attach-pid
• --wait-for — tells the debugger to wait for a process with the given pid or name to launch before attaching. It's patient, it's loyal, it's waiting for you. 🥺
• -w — alias for --wait-for

✨ COMMANDS ✨

• --batch — tells the debugger to run the commands from -s, -S, -o & -O, and then quit. Run it and dip. 🚪
• -b — alias for --batch
• -K <value> — alias for --source-on-crash
• -k <value> — alias for --one-line-on-crash
• --local-lldbinit — allow the debugger to parse the .lldbinit files in the current working directory, unless --no-lldbinit is passed. Local files only, very neighborhood-coded. 🏡
• --no-lldbinit — do not automatically parse any .lldbinit files.
• --one-line-before-file <command> — tells the debugger to execute this one-line lldb command before any file provided on the command line has been loaded.
• --one-line-on-crash <command> — when in batch mode, tells the debugger to run this one-line lldb command if the target crashes. 💀
• --one-line <command> — tells the debugger to execute this one-line lldb command after any file provided on the command line has been loaded.
• -O <value> — alias for --one-line-before-file
• -o <value> — alias for --one-line
• -Q — alias for --source-quietly
• --source-before-file <file> — tells the debugger to read in and execute the lldb commands in the given file, before any file has been loaded.
• --source-on-crash <file> — when in batch mode, tells the debugger to source this file of lldb commands if the target crashes. 🚨
• --source-quietly — tells the debugger not to echo commands while sourcing files or one-line commands provided on the command line. shhh, it's a secret. 🤫
• --source <file> — tells the debugger to read in and execute the lldb commands in the given file, after any file has been loaded.
• -S <value> — alias for --source-before-file
• -s <value> — alias for --source
• -x — alias for --no-lldbinit

🔥 OPTIONS 🔥

• --arch <architecture> — tells the debugger to use the specified architecture when starting and running the program. Gotta pick your vibe. 🌈
• -a <value> — alias for --arch
• --core <filename> — tells the debugger to use the full path to <filename> as the core file.
• -c <value> — alias for --core
• --debug — tells the debugger to print out extra information for debugging itself. Debugception, lowkey. 🌀
• -d — alias for --debug
• --editor — tells the debugger to open source files using the host's "external editor" mechanism.
• -e — alias for --editor
• --file <filename> — tells the debugger to use the file <filename> as the program to be debugged.
• -f <value> — alias for --file
• --help — prints out the usage information for the LLDB debugger. Bestie behavior honestly. 🫶
• -h — alias for --help
• --no-use-colors — do not use colors. (sad, but valid)
• --version — prints out the current version number of the LLDB debugger.
• -v — alias for --version
• -X — alias for --no-use-color

not me pointing out that -X is an alias for --no-use-color and not --no-use-colors — yep, that's literally what the page says, singular, no cap. 👀

💜 REPL 💜

• -r=<flags> — alias for --repl=<flags>
• --repl-language <language> — chooses the language for the REPL.
• --repl=<flags> — runs lldb in REPL mode with a stub process with the given flags.
• --repl — runs lldb in REPL mode with a stub process.
• -R <value> — alias for --repl-language
• -r — alias for --repl

🧚 SCRIPTING 🧚

• -l <value> — alias for --script-language
• --print-script-interpreter-info — prints out a json dictionary with information about the scripting language interpreter. json!! 🍓
• --python-path — prints out the path to the lldb.py file for this version of lldb.
• -P — alias for --python-path
• --script-language <language> — tells the debugger to use the specified scripting language for user-defined scripts.

⭐ EXAMPLES ⭐

The debugger can be started in several modes.

Passing an executable as a positional argument prepares lldb to debug the given executable. To disambiguate between arguments passed to lldb and arguments passed to the debugged executable, arguments starting with a - must be passed after --.

lldb --arch x86_64 /path/to/program program argument -- --arch armv7

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

lldb --arch x86_64 -- /path/to/program program argument --arch armv7

Passing one of the attach options causes lldb to immediately attach to the given process.

lldb -p <pid>
lldb -n <process-name>

Passing --repl starts lldb in REPL mode.

lldb -r

Passing --core causes lldb to debug the core file.

lldb -c /path/to/core

Command options can be combined with these modes and cause lldb to run the specified commands before or after events, like loading the file or crashing, in the order provided on the command line.

lldb -O 'settings set stop-disassembly-count 20' -o 'run' -o 'bt'
lldb -S /source/before/file -s /source/after/file
lldb -K /source/before/crash -k /source/after/crash

Note: In REPL mode no file is loaded, so commands specified to run after loading the file (via -o or -s) will be ignored.

---

and that's the whole page bestie, you ate that. 🎀 this was lldb 16, from April 2024, and you read the entire thing which is honestly main character energy. go debug something iconic. 💖✨🦋👑