LLDB(1)

📦 version 11.1.0, in ubuntu jammy

💖 LLDB(1) 💖

okay bestie, buckle up 🎀 this is the User Commands manual page for lldb — specifically lldb 11 — and by the end of it you're gonna be debugging like the main character you are. no cap. ✨

🌸 NAME 🌸

lldb — manual page for lldb 11

🦋 DESCRIPTION 🦋

OVERVIEW: LLDB

USAGE:

lldb [options]

like, that's it. that's the whole vibe. 💅 now let's get into it.

🫶 ATTACHING:

  • --attach-name <name> — tells the debugger to attach to a process with the given name. just, like, slide into its DMs.
  • --attach-pid <pid> — tells the debugger to attach to a process with the given pid. very specific. very targeted. we love that for us.
  • -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 giving patient. it's giving "i'll be here when you're ready." 💜
  • -w — alias for --wait-for

✨ COMMANDS:

  • --batch — tells the debugger to run the commands from -s, -S, -o & -O, and then quit. no lingering, no small talk, it's out. 👑
  • -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.
  • --no-lldbinit — do not automatically parse any '.lldbinit' files. boundaries!! 🚧
  • --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. 😭 (it crashed)
  • --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 to execute this one-line lldb command before any file has been loaded.
  • --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.
  • -a <value> — alias for --arch
  • --capture-path <filename> — tells the debugger to use the given filename for the reproducer.
  • --capture — tells the debugger to capture a reproducer. 📸
  • --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. debugging the debugger, iconic behavior fr fr.
  • -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)
  • --replay <filename> — tells the debugger to replay a reproducer from <filename>.
  • --reproducer-generate-on-exit — generate reproducer on exit.
  • --reproducer-no-generate-on-signal — don't generate reproducer when a signal is received.
  • --reproducer-no-version-check — disable the reproducer version check.
  • --version — prints out the current version number of the LLDB debugger.
  • -v — alias for --version
  • -X — alias for --no-use-color

🧚 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
  • --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. slay, versatile, multitalented.

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 arvm7

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

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

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!! 🫶 this was lldb 11, dated January 2022, and you absolutely ate this read. go forth and debug, you gorgeous genius. 💖✨🎀🦋

📦 where this page comes from