LLDB (debugger)

LLDB
Developer(s)	LLVM Developer Group
Stable release	19.1.3 / 30 October 2024;41 days ago
Repository	github.com/llvm/llvm-project ;
Written in	C++
Operating system	macOS i386 and x86-64, Linux, FreeBSD, NetBSD, Windows
Type	Debugger
License	UIUC (BSD-style); Apache License 2.0 with LLVM Exceptions (v9.0.0 or later)
Website	lldb.llvm.org

Last updated December 11, 2024

The LLDB Debugger (LLDB) is the debugger component of the LLVM project. It is built as a set of reusable components which extensively use existing libraries from LLVM, such as the Clang expression parser and LLVM disassembler. LLDB is free and open-source software under the University of Illinois/NCSA Open Source License,^[3] a BSD-style permissive software license. Since v9.0.0, it was relicensed to the Apache License 2.0 with LLVM Exceptions.^[2]

Current state

LLDB supports debugging of programs written in C, Objective-C, and C++. The Swift community maintains a version which adds support for the language. Free Pascal and the Lazarus IDE can use LLDB as backend for their own FpDebug engine.

The LLDB debugger is known to work on macOS, Linux, FreeBSD, NetBSD and Windows,^[4] and supports i386, x86-64, and ARM instruction sets.^[5] LLDB is the default debugger for Xcode 5 and later. Android Studio also uses LLDB for debug.^[6] LLDB can be used from other IDEs, including Visual Studio Code,^[7] C++Builder,^[8] Eclipse,^[9] and CLion.^[10]

Features matrix ^[5]
Feature	FreeBSD	Linux	macOS	NetBSD	Windows
Backtracing
Breakpoints
C++11					?
Command-line lldb tool
Core file debugging
Debugserver (remote debugging)
Disassembly
Expression evaluation	Works with some bugs	Works with some bugs		Works with some bugs	Works with some bugs
JIT debugging	?	Symbolic debugging only	Untested	Work In Progress
Objective-C 2.0:	?	—		?	—

Examples of commands

`lldb program`	Debug "program" (from the shell)
`run`	Run the loaded program
`break set -n main`	Set a breakpoint at the start of function "main"
`bt`	Backtrace (in case the program crashed)
`register read`	Dump all registers
`di -n main`	Disassemble the function "main"

An example session

Consider the following incorrect program written in C:

#include<stdio.h>intmain(void){charmsg="Hello, world!\n";printf("%s",msg);return0;}

Using the clang compiler on macOS, the code above can be compiled using the -g flag to include appropriate debug information on the binary generated—including the source code—making it easier to inspect it using LLDB. Assuming that the file containing the code above is named test.c, the command for the compilation could be:

$ clang-Wno-error=int-conversion-gtest.c-otest

And the binary can now be run:

$ ./test Segmentation fault

Since the example code, when executed, generates a segmentation fault, lldb can be used to inspect the problem:

$ lldbtest(lldb)target create "test"Current executable set to 'test' (x86_64).(lldb)runProcess 70716 launched: '/Users/wikipedia/test' (x86_64)Process 70716 stopped* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0xffffff90)    frame #0: 0x00007fff6c7c46f2 libsystem_platform.dylib`_platform_strlen + 18libsystem_platform.dylib`_platform_strlen:->  0x7fff6c7c46f2 <+18>: pcmpeqb xmm0, xmmword ptr [rdi]    0x7fff6c7c46f6 <+22>: pmovmskb esi, xmm0    0x7fff6c7c46fa <+26>: and    rcx, 0xf    0x7fff6c7c46fe <+30>: or     rax, -0x1Target 0: (test) stopped.

The problem occurs when calling the function strlen , but we can run a backtrace to identify the exact line of code that is causing the problem:

(lldb)bt* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0xffffff90)  * frame #0: 0x00007fff6c7c46f2 libsystem_platform.dylib`_platform_strlen + 18    frame #1: 0x00007fff6c66b16a libsystem_c.dylib`__vfprintf + 8812    frame #2: 0x00007fff6c6911c3 libsystem_c.dylib`__v2printf + 475    frame #3: 0x00007fff6c668e22 libsystem_c.dylib`vfprintf_l + 54    frame #4: 0x00007fff6c666f72 libsystem_c.dylib`printf + 174    frame #5: 0x0000000100000f6d test`main at test.c:5:2    frame #6: 0x00007fff6c5dc3d5 libdyld.dylib`start + 1(lldb)source list   3    int main(void) {   4     char msg = "Hello, world!\n";   5     printf("%s", msg);   6     return 0;   7    }

From the line beginning with frame #5, LLDB indicates that the error is at line 5 of test.c. Running source list, we see that this refers to the call to printf. According to the exception code EXC_BAD_ACCESS from the backtrace, strlen is trying to read from a region of memory it does not have access to by dereferencing an invalid pointer.^[11] Returning to the source code, we see that the variable msg is of type char but contains a string instead of a character. To fix the problem, we modify the code to indicate that msg is a pointer to a string of chars by adding the * operator:

#include<stdio.h>intmain(void){char*msg="Hello, world!\n";printf("%s",msg);return0;}

After recompiling and running the executable again, LLDB now gives the correct result:

(lldb)target create "test"Current executable set to 'test' (x86_64).(lldb)runProcess 93319 launched: '/Users/wikipedia/test' (x86_64)Hello, world!Process 93319 exited with status = 0 (0x00000000)(lldb)

LLDB runs the program, which prints the output of printf to the screen. After the program exits normally, LLDB indicates that the process running the program has completed, and prints its exit status.

Related Research Articles

The GNU Debugger (GDB) is a portable debugger that runs on many Unix-like systems and works for many programming languages, including Ada, Assembly, C, C++, D, Fortran, Haskell, Go, Objective-C, OpenCL C, Modula-2, Pascal, Rust, and partially others.

In computing, a segmentation fault or access violation is a fault, or failure condition, raised by hardware with memory protection, notifying an operating system (OS) the software has attempted to access a restricted area of memory. On standard x86 computers, this is a form of general protection fault. The operating system kernel will, in response, usually perform some corrective action, generally passing the fault on to the offending process by sending the process a signal. Processes can in some cases install a custom signal handler, allowing them to recover on their own, but otherwise the OS default signal handler is used, generally causing abnormal termination of the process, and sometimes a core dump.

x86 assembly language is the name for the family of assembly languages which provide some level of backward compatibility with CPUs back to the Intel 8008 microprocessor, which was launched in April 1972. It is used to produce object code for the x86 class of processors.

D, also known as dlang, is a multi-paradigm system programming language created by Walter Bright at Digital Mars and released in 2001. Andrei Alexandrescu joined the design and development effort in 2007. Though it originated as a re-engineering of C++, D is now a very different language. As it has developed, it has drawn inspiration from other high-level programming languages. Notably, it has been influenced by Java, Python, Ruby, C#, and Eiffel.

OpenMP is an application programming interface (API) that supports multi-platform shared-memory multiprocessing programming in C, C++, and Fortran, on many platforms, instruction-set architectures and operating systems, including Solaris, AIX, FreeBSD, HP-UX, Linux, macOS, and Windows. It consists of a set of compiler directives, library routines, and environment variables that influence run-time behavior.

Splint, short for Secure Programming Lint, is a programming tool for statically checking C programs for security vulnerabilities and coding mistakes. Formerly called LCLint, it is a modern version of the Unix lint tool.

The syntax of the C programming language is the set of rules governing writing of software in C. It is designed to allow for programs that are extremely terse, have a close relationship with the resulting object code, and yet provide relatively high-level data abstraction. C was the first widely successful high-level language for portable operating-system development.

In computing, POSIX Threads, commonly known as pthreads, is an execution model that exists independently from a programming language, as well as a parallel execution model. It allows a program to control multiple different flows of work that overlap in time. Each flow of work is referred to as a thread, and creation and control over these flows is achieved by making calls to the POSIX Threads API. POSIX Threads is an API defined by the Institute of Electrical and Electronics Engineers (IEEE) standard POSIX.1c, Threads extensions .

LLVM is a set of compiler and toolchain technologies that can be used to develop a frontend for any programming language and a backend for any instruction set architecture. LLVM is designed around a language-independent intermediate representation (IR) that serves as a portable, high-level assembly language that can be optimized with a variety of transformations over multiple passes. The name LLVM originally stood for Low Level Virtual Machine, though the project has expanded and the name is no longer officially an initialism.

A variadic macro is a feature of some computer programming languages, especially the C preprocessor, whereby a macro may be declared to accept a varying number of arguments.

gtkmm is the official C++ interface for the popular GUI library GTK. gtkmm is free software distributed under the GNU Lesser General Public License (LGPL).

Code::Blocks is a free, open-source, cross-platform IDE that supports multiple compilers including GCC, Clang and Visual C++. It is developed in C++ using wxWidgets as the GUI toolkit. Using a plugin architecture, its capabilities and features are defined by the provided plugins. Currently, Code::Blocks is oriented towards C, C++, and Fortran. It has a custom build system and optional Make support.

select is a system call and application programming interface (API) in Unix-like and POSIX-compliant operating systems for examining the status of file descriptors of open input/output channels. The select system call is similar to the poll facility introduced in UNIX System V and later operating systems. However, with the c10k problem, both select and poll have been superseded by the likes of kqueue, epoll, /dev/poll and I/O completion ports.

Clang is a compiler front end for the programming languages C, C++, Objective-C, Objective-C++, and the software frameworks OpenMP, OpenCL, RenderScript, CUDA, SYCL, and HIP. It acts as a drop-in replacement for the GNU Compiler Collection (GCC), supporting most of its compiling flags and unofficial language extensions. It includes a static analyzer, and several code analysis tools.

Vala is an object-oriented programming language with a self-hosting compiler that generates C code and uses the GObject system.

Christopher Arthur Lattner is an American software engineer and creator of LLVM, the Clang compiler, the Swift programming language and the MLIR compiler infrastructure.

Blocks are a non-standard extension added by Apple Inc. to Clang's implementations of the C, C++, and Objective-C programming languages that uses a lambda expression-like syntax to create closures within these languages. Blocks are supported for programs developed for Mac OS X 10.6+ and iOS 4.0+, although third-party runtimes allow use on Mac OS X 10.5 and iOS 2.2+ and non-Apple systems.

Bionic is an implementation of the C standard library, developed by Google for its Android operating system. It differs from the GNU C Library (glibc) in being designed for devices with less memory and processor power than a typical Linux system. It is a combination of new code and code from FreeBSD, NetBSD, and OpenBSD released under a BSD license, rather than glibc, which uses the GNU Lesser General Public License. This difference was important in the early days of Android, when static linking was common, and since Bionic has its own application binary interface, it cannot be replaced by a different libc without breaking all existing apps.

Objective-C is a high-level general-purpose, object-oriented programming language that adds Smalltalk-style message passing (messaging) to the C programming language. Originally developed by Brad Cox and Tom Love in the early 1980s, it was selected by NeXT for its NeXTSTEP operating system. Due to Apple macOS’s direct lineage from NeXTSTEP, Objective-C was the standard language used, supported, and promoted by Apple for developing macOS and iOS applications from 1997, when Apple purchased NeXT until the introduction of the Swift language in 2014.

A code sanitizer is a programming tool that detects bugs in the form of undefined or suspicious behavior by a compiler inserting instrumentation code at runtime. The class of tools was first introduced by Google's AddressSanitizer of 2012, which uses directly mapped shadow memory to detect memory corruption such as buffer overflows or accesses to a dangling pointer (use-after-free).

References

↑ "Release 19.1.3". 30 October 2024. Retrieved 15 November 2024.
1 2 LICENSE.TXT, llvm.org, retrieved 2019-09-24
↑ "LLVM Release License"
↑ "LLVM Project Blog". 20 January 2015.
1 2 "LLDB Status" . Retrieved January 31, 2022.
↑ "Debug your app".
↑ "Add a new tool named "lldb-vscode" that implements the Visual Studio Code Debug Adaptor Protocol".
↑ "11.3 introduces a new LLDB-based debugger for macOS Intel and 32-bit Android. With 11.3 all non-Windows platform debuggers across Delphi and C++ have moved to LLDB architecture".
↑ "CDT/Useer/FAQ".
↑ "LLDB CLion Blog". 7 October 2024.
↑ "Technical Note TN2151: Understanding and Analyzing Application Crash Reports". Documentation Archive. Apple Developer. Retrieved 13 February 2020.

External links

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.

[wikidata-ea2a7b012a7fb4e57908d7dcac5ce6811fbe0763-v18-1] "Release 19.1.3". 30 October 2024. Retrieved 15 November 2024.

[License-2] 1 2 LICENSE.TXT, llvm.org, retrieved 2019-09-24

[license-3] "LLVM Release License"

[4] "LLVM Project Blog". 20 January 2015.

[status-5] 1 2 "LLDB Status" . Retrieved January 31, 2022.

[6] "Debug your app".

[7] "Add a new tool named "lldb-vscode" that implements the Visual Studio Code Debug Adaptor Protocol".

[8] "11.3 introduces a new LLDB-based debugger for macOS Intel and 32-bit Android. With 11.3 all non-Windows platform debuggers across Delphi and C++ have moved to LLDB architecture".

[9] "CDT/Useer/FAQ".

[10] "LLDB CLion Blog". 7 October 2024.

[11] "Technical Note TN2151: Understanding and Analyzing Application Crash Reports". Documentation Archive. Apple Developer. Retrieved 13 February 2020.

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]