LLDB

Overview

LLDB is an open-source debugger built on reusable LLVM components, aimed at developers working in C-family languages. It is especially compelling in Xcode workflows and where its API or remote-debugging support is useful; Windows support remains a less mature fit.

Its combination of Clang-based expression evaluation, broad debugging controls and a zero-cost license makes it a capable general choice. The trade-off is that some lldb-dap operations are absent and Windows support is still developing.

Key features

Debugging and expression evaluation

LLDB supports C, C++, and Objective-C debugging on desktop and iOS devices and simulators; its expression evaluator also handles Objective-C++. Clang infrastructure lets it evaluate current language features, including multiline expressions and just-in-time evaluation where supported. That makes inspecting and experimenting with program state a natural part of its workflow, though JIT availability depends on the context.

Breakpoints, including conditional and exception breakpoints, watchpoints, process launching, and attachment cover common debugging needs. LLDB can also debug core dumps. It does not offer time-travel debugging, so developers who need to move backward through execution should look elsewhere.

APIs, scripting, and integrations

A public object-oriented C++ API is available through a shared library, alongside Python bindings. These extend LLDB beyond interactive debugging: the API can support symbolication, disassembly, and inspection of object and symbol files. The project also describes a Model Context Protocol integration.

For compatible editors and IDEs, lldb-dap exposes LLDB through the Debug Adapter Protocol. Its documented requests include function, conditional, data, and instruction breakpoints, memory reads and writes, and disassembly. It does not support step-back, variable setting, goto-target, or terminate requests. Those omissions matter when an editor workflow relies on those controls; users can obtain the binary through a toolchain, LLVM release package, system package manager, or source build.

Remote debugging and safety

LLDB documents remote debugging for Linux, Windows, Android, and iOS. It also avoids sourcing a current-directory .lldbinit file by default for security reasons, a sensible safeguard against automatically running project-directory configuration.

Pricing

LLDB is free and open source under the Apache 2.0 License with LLVM exceptions. The LLDB plan costs 0.00 USD per free and includes the debugger; there is no free trial because access does not require a paid plan. That makes it suitable for individual developers and teams alike, without a stated seat fee or free-plan quota.

Platforms

LLDB’s supported targets include macOS, iOS, tvOS, watchOS, Linux, FreeBSD, NetBSD, Windows, and Android. It is the default debugger in Xcode on macOS, a strong fit for Apple development. Windows support is under active development: basic functionality is expected to work, while ARM and AArch64 support is more experimental. Teams depending on those Windows architectures should account for that maturity gap.

Who it's for

LLDB suits developers debugging C, C++, Objective-C, or Objective-C++ who want a free debugger with programmable APIs, IDE integration, or remote-debugging options. It is particularly attractive to Xcode users and developers already working with LLVM. It is less suitable when time-travel debugging is essential, when a lldb-dap workflow needs one of its unsupported requests, or when experimental Windows architecture support is unacceptable.

Pros and cons

• Pros: No-cost access under an open-source license avoids per-seat pricing.
• Pros: Clang-based expression evaluation covers four C-family languages, with multiline expressions and JIT evaluation where supported.
• Pros: C++ and Python interfaces enable scripting and uses beyond interactive debugging, including symbolication and disassembly.
• Pros: Broad desktop and mobile targets, remote-debugging support, and Xcode integration give it reach across varied workflows.
• Cons: No time-travel debugging limits options for developers who need to revisit earlier execution states.
• Cons: lldb-dap omits step-back, variable setting, goto-target, and terminate requests, which can constrain editor-driven debugging.
• Cons: Windows support is still developing, with ARM and AArch64 described as more experimental.

Alternatives

Browse other debuggers if LLDB’s missing time-travel capability or lldb-dap request support does not fit your workflow.

• GDB is another free debugger for Linux, macOS, and Windows, under the GNU General Public License.
• FlowStorm is a free and open-source option for Linux, macOS, Windows, and self-hosted environments.
• IDA Pro is worth considering when disassembly is the priority: its free plan covers x86-32 and x86-64 disassembly and two cloud-based decompilers, while IDA Pro Essential costs 1099.00 USD.
• RenderDoc is a free, MIT-licensed option for Android, Linux, and Windows.
• Xdebug is a freemium alternative for Linux, macOS, Windows, web, and self-hosted environments.
• Delve is a free alternative for Linux, macOS, Windows, API, and self-hosted environments.
• SEGGER Ozone is a paid alternative for Linux, macOS, and Windows.
• UDB is a paid option with a free trial for Linux and extension environments.

Verdict

Choose LLDB if you need a free, extensible debugger for C-family development, particularly in Xcode or LLVM-centered workflows. Its APIs, expression evaluator, and broad target coverage are substantial strengths; look elsewhere if time-travel debugging is required, lldb-dap’s missing requests are blockers, or developing Windows support does not meet your needs.