LLDB

Overview

LLDB is a debugger for developers working with programs built around LLVM-supported languages and targets. It is a strong fit for C-family development, especially in Xcode, but its uneven Windows maturity and missing lldb-dap operations matter if those are central to your workflow.

Key features

Debugging and expression evaluation

LLDB provides breakpoints, watchpoints, process launching, and attachment, plus conditional and exception breakpoints and core-dump debugging. That range supports routine inspection and control of a program, though the absence of time-travel debugging means it is not the choice for developers who need to rewind execution to investigate a past state.

Its Clang-based evaluator handles current C, C++, Objective-C, and Objective-C++ expressions, including multiline expressions and just-in-time evaluation where supported. This is useful for inspecting and working with language expressions during debugging; the qualification matters, since JIT evaluation is not universal.

Editor integration and APIs

LLDB is the default debugger in Xcode on macOS. The lldb-dap adapter exposes debugger functions to compatible editors and IDEs such as Visual Studio Code, Emacs, vim, and neovim. It supports function, conditional, data, and instruction breakpoints, memory reads and writes, and disassembly requests. However, it does not support step-back, setting a variable, goto-target, or terminate requests, so workflows depending on those adapter operations may need another debugger or a different route.

Developers can build on its public object-oriented C++ API, distributed through a shared library, and Python bindings. Beyond interactive debugging, these interfaces can support scripting, symbolication, disassembly, and object- or symbol-file inspection. LLDB also documents an integration using the Model Context Protocol. The lldb-dap binary can be obtained through a toolchain, an LLVM release or system package manager, or a source build, giving teams several ways to provision it.

Pricing

LLDB is free and open source under the Apache 2.0 License with LLVM exceptions. Its LLDB plan costs 0.00 USD per free. There is no free trial because no paid plan is needed to use the debugger. No seat or usage quota is attached to the free plan.

Platforms

LLDB targets macOS, iOS, tvOS, watchOS, Linux, FreeBSD, NetBSD, Windows, and Android; remote debugging is documented for Linux, Windows, Android, and iOS. Its language support covers C, C++, and Objective-C debugging on desktop and iOS devices and simulators, while the evaluator also handles Objective-C++. On Windows, basic functionality is expected to work, but support remains under active development and ARM and AArch64 support is more experimental. That makes LLDB a less settled choice for Windows teams, particularly those targeting those architectures.

For security, LLDB does not source a current-directory .lldbinit file by default. This reduces the risk of automatically executing an untrusted configuration, though developers who rely on such files must account for the behavior.

Who it's for

LLDB suits developers building and debugging C-family software across Apple platforms and LLVM-supported desktop and mobile targets, especially teams already using Xcode or compatible editor integrations. Its reusable APIs also make it relevant to developers building debugger tooling or using symbolication and disassembly. It is a weaker fit for workflows that require time-travel debugging, the unsupported lldb-dap operations, or mature Windows support on ARM and AArch64.

Pros and cons

• Pros: Broad C-family language support, including Objective-C++ expression evaluation, gives developers one debugger for closely related languages.
• Pros: Xcode's default debugger status and lldb-dap support for several editors make LLDB practical in Apple and compatible-editor workflows.
• Pros: A public C++ API and Python bindings extend its usefulness beyond interactive debugging to scripting and binary inspection tasks.
• Cons: No time-travel debugging leaves developers without a rewind-based way to trace execution.
• Cons: lldb-dap lacks step-back, variable-setting, goto-target, and terminate requests, which can constrain editor-driven workflows.
• Cons: Windows support is still developing, with ARM and AArch64 explicitly more experimental.

Alternatives

For a debugger directory, browse Debuggers. Choose RenderDoc instead if its Android, Linux, and Windows platform range better matches your target; it is also free and open source, under the MIT license. FLEX is an iOS-only free alternative. PonyDebugger is another free option if its web, macOS, and iOS platform coverage suits your needs.

IDA Pro offers a free IDA Free plan with x86-32 and x86-64 disassembly, two cloud-based decompilers, and a named license on macOS, Linux, and Windows; choose it when those capabilities fit your work, or consider IDA Pro Essential at 1099.00 USD. FlowStorm is a free, open-source option for Linux, macOS, Windows, and self-hosted use. GDB is a free alternative with source code available under the GNU General Public License. Delve is another free option, with Linux, macOS, Windows, API, and self-hosted platform coverage.

Xdebug may suit readers seeking a freemium option across Linux, macOS, self-hosted, web, and Windows. Its Pro plan costs 200.00 GBP per year and includes one developer, email technical support at medium issue priority, an opt-in monthly newsletter, and an invoice.

Verdict

Choose LLDB for free, capable C-family debugging across Apple platforms and a broad set of documented targets, particularly if you work in Xcode or use its APIs and editor integrations. Look elsewhere if your workflow depends on time-travel debugging, the lldb-dap operations it omits, or dependable Windows ARM and AArch64 support.