LLDB

LLDB is an open-source debugger for developers working with C, C++, Objective-C, or Objective-C++ code. It is the natural fit for Xcode users and for teams that want a debugger they can embed or script. Its broad debugger and API capabilities come with uneven support across platforms and no time-travel debugging.

Overview

LLDB is built from reusable components drawing on LLVM libraries, including Clang’s expression parser and LLVM’s disassembler. It can launch programs, attach to running processes, and work with breakpoints and watchpoints. The project code is licensed under Apache 2.0 with LLVM exceptions, making LLDB a capable no-cost option for individual developers and teams that can accommodate its platform-specific limitations.

Key features

Expression evaluation and control

Clang-based expression evaluation covers current C, C++, Objective-C, and Objective-C++ language features. Multiline expressions and just-in-time evaluation are supported where the context allows them, which is useful when inspecting or evaluating code during a debugging session. Conditional and exception breakpoints, watchpoints, and core-dump debugging cover common ways to narrow down failures, but LLDB does not offer time-travel debugging for tracing execution backward.

APIs, scripting, and editor integration

A public object-oriented C++ API is exposed through a shared library, with Python bindings for scripting. That gives developers room to build tooling around the debugger; the API can also support symbolication, disassembly, and inspection of object and symbol files. LLDB also documents an integration using the Model Context Protocol.

For compatible editors and IDEs, lldb-dap exposes LLDB through the Debug Adapter Protocol. It documents function, conditional, data, and instruction breakpoints, along with memory read and write and disassembly requests. It does not support step-back, setting a variable, goto-target, or terminate requests, so editor users should check whether those omissions matter to their workflow. The lldb-dap binary can come from an LLVM release package, a toolchain or system package manager, or a source build.

Remote debugging and configuration

LLDB documents remote debugging for Linux, Windows, Android, and iOS, extending its use beyond programs running on the debugger’s own system. For security, it does not source a current-directory .lldbinit file by default; developers relying on project-local startup configuration need to account for that safeguard.

Pricing

LLDB’s free plan costs nothing and is open source; there is no free trial because the software is free to use. It supports C, C++, Objective-C, and Objective-C++, with targets including macOS, iOS, tvOS, watchOS, Linux, FreeBSD, NetBSD, Windows, and Android. There are no paid tiers or seat limits to weigh against the free plan. Its main trade-off is not price but platform maturity: Windows support is under active development, and ARM and AArch64 support there is more experimental.

Platforms

LLDB is the default debugger in Xcode on macOS, and its documented language support covers debugging C, Objective-C, and C++ on desktop and iOS devices and simulators. The project lists macOS, Linux, FreeBSD, NetBSD, and Windows support, while the plan’s target platforms also include iOS, tvOS, watchOS, and Android. Windows users should expect an actively developing implementation rather than the same level of assurance as established targets; ARM and AArch64 on Windows are especially experimental. Check target-specific support before committing a workflow to those configurations.

Who it's for

LLDB is best suited to developers already using Xcode, LLVM-based toolchains, or editors with Debug Adapter Protocol support, especially when C-family debugging and scripting or embedding through the API are priorities. It is less suitable for teams that require time-travel debugging, need every DAP request supported, or depend on mature Windows ARM-family debugging. Documentation points users to a forum or LLVM Discord for discussion and provides routes for bug reports and code reviews, which may suit developers comfortable engaging with an open-source project community.

Pros and cons

• Pros: Free, open-source access to a debugger with C-family expression evaluation, breakpoints, watchpoints, and core-dump debugging makes it useful across a range of development workflows.
• Pros: The public C++ API and Python bindings support custom tooling, while lldb-dap connects the debugger to compatible editors and IDEs.
• Pros: Remote debugging and documented mobile targets extend LLDB beyond local desktop sessions.
• Cons: No time-travel debugging means developers cannot use LLDB to step backward through execution.
• Cons: lldb-dap lacks step-back, variable-setting, goto-target, and terminate requests, which can constrain editor-driven debugging.
• Cons: Windows is still under active development, with ARM and AArch64 support more experimental.

Alternatives

Browse other debuggers if LLDB’s platform maturity or workflow limits do not fit your needs.

• Delve is a free alternative for readers considering a debugger on Linux, macOS, Windows, or a self-hosted setup.
• IDA Pro is an alternative for readers who need disassembly: IDA Free costs nothing and covers x86-32 and x86-64 disassembly with two cloud-based decompilers on a named license; IDA Pro Essential costs 1099.00 USD.
• Xdebug is a freemium alternative for Linux, macOS, Windows, web, or self-hosted environments; its Pro plan is £200 a year for one developer and includes e-mail technical support.
• FlowStorm is a free and open-source option for Linux, macOS, Windows, or self-hosted use.
• GDB is a free, source-available alternative for Linux, macOS, or Windows.
• OpenOCD is a free alternative for Windows, macOS, or Linux.
• Perl Debugger is a free alternative for Linux, macOS, or Windows.
• PonyDebugger is a free alternative for web, macOS, or iOS.

Verdict

Choose LLDB if you need a free C-family debugger with strong Xcode alignment, reusable APIs, and options to integrate it into editor or remote-debugging workflows. Its limits are clear: it cannot trace execution backward, some DAP requests are absent, and Windows ARM-family support remains experimental. Developers whose targets and workflow fit its established capabilities have a flexible debugger without a license cost; those needing the missing controls or more settled support on those Windows targets should consider another fit.