Install lldb with Homebrew, apk, apt, dnf, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Package manager page

Commands and aliases

• lldb
• lldb-argdumper
• lldb-dap
• lldb-instr
• lldb-mcp
• lldb-server
• lldb-tblgen
• yaml2macho-core

Project history

LLVM announced LLDB as a new subproject in June 2010. It was designed as modular debugger infrastructure reusing LLVM's disassembler, code generator, JIT, and Clang expression parser rather than as a monolithic command-line debugger.

The project matured into both a command-line debugger and a reusable API surface. Its source now resides in the LLVM monorepo, and it is released under Apache-2.0 with the LLVM exception.

Adoption history

LLDB became the default debugger in Xcode and expanded beyond its original macOS implementation to Linux, FreeBSD, NetBSD, and Windows. LLVM project material described it by 2016 as being used by millions of developers and as infrastructure for additional language debuggers.

How it is used

Users commonly launch `lldb` with an executable, set breakpoints, inspect threads and variables, evaluate expressions, analyze crashes, or attach to running processes. Advanced workflows use Python scripts, the public debugger APIs, `lldb-server`, and IDE integrations.

LLDB reads user commands, aliases, and settings from `.lldbinit` files. Application-specific and language-REPL initialization files take precedence over the general home-directory file; a working-directory `.lldbinit` is not sourced by default for security reasons.

Why package nerds care

LLDB is a foundational developer package: distributions package its CLI and libraries separately or alongside LLVM, while IDEs consume its debugger APIs. Its close coupling to Clang, LLVM release cadence, Python scripting support, remote-debugging components, and platform-specific builds make version and packaging details operationally important.

Timeline

• 2010: LLVM publicly announced LLDB as a new subproject.
• 2016: LLVM maintainers described established macOS and Linux use, growing Windows support, and adoption through IDE integrations.
• Present: LLDB is developed in the LLVM monorepo and shipped by major Unix-like package ecosystems.

Related projects

• LLVM supplies core compiler infrastructure used by LLDB.
• Clang supplies LLDB's C-family expression parser and type-system integration.
• Xcode uses LLDB as its default debugger.
• GDB is the established debugger for which LLDB provides an official command-translation map.

Sources

• https://blog.llvm.org/2010/06/new-lldb-debugger.html
• https://lists.llvm.org/pipermail/lldb-dev/2016-August/010870.html
• https://lldb.llvm.org/
• https://lldb.llvm.org/resources/build.html
• source_facts.package-manager