Home
last modified time | relevance | path

Searched refs:LLDB (Results 1 – 25 of 154) sorted by relevance

1234567

/llvm-project-15.0.7/lldb/docs/use/
H A Dlinks.rst4 This page contains links to external resources on how to use LLDB. Being
10 `Dancing in the Debugger — A Waltz with LLDB (2014)`_
19 `LLDB: Beyond “po” (2019)`_
27 `Advanced Debugging with Xcode and LLDB (2018)`_
36 `Debugging with LLDB (2012)`_
39 LLDB is the next-generation debugger for macOS and iOS. Get an
45 `Migrating from GDB to LLDB (2011)`_
59 A book about using LLDB on Apple platforms.
70 `DerekSelander/LLDB`_
73 A collection of LLDB aliases/regexes and Python scripts.
[all …]
H A Dqemu-testing.rst1 Testing LLDB using QEMU
10 QEMU can be used to test LLDB in an emulation environment in the absence of
12 environment for testing LLDB.
15 setup a virtual LLDB testing environment using QEMU. The scripts currently work
29 Given below are some examples of common use-cases of LLDB QEMU testing
128 …s compile LLDB server for AArch64 Linux: Please visit https://lldb.llvm.org/resources/build.html f…
130 * Transfer LLDB server executable to emulation environment
H A Dvariable.rst7 LLDB has a data formatters subsystem that allows users to define custom display
10 Usually, when you type ``frame variable`` or run some expression LLDB will
25 as to how variables should be displayed. The LLDB type command allows you to do
133 at the LLDB command line.
210 and --skip-references (-r). These two options prevent LLDB from applying a
375 processed by LLDB to generate the summary.
681 LLDB to detect the end of the pointed data.
969 including it in the range of children displayed by LLDB. For example,
1009 children provider in LLDB:
1150 compiled into the LLDB core).
[all …]
/llvm-project-15.0.7/lldb/docs/
H A Dindex.rst1 .. title:: LLDB Homepage
3 The LLDB Debugger
6 Welcome to the LLDB documentation!
8 LLDB is a next generation, high-performance debugger. It is built as a set of
12 LLDB is the default debugger in Xcode on macOS and supports debugging C,
15 All of the code in the LLDB project is available under the
20 Using LLDB
23 For an introduction into the LLDB command language, head over to the `LLDB
35 LLDB converts debug information into Clang types so that it can
62 Sharing the LLDB API allows LLDB to not only be used for debugging, but also
[all …]
H A Ddoxygen-mainpage.dox1 /// @mainpage LLDB
4 /// Welcome to LLDB.
6 /// This documentation describes both the private and public interface of LLDB.
7 /// There are no instructions here on how to use LLDB, only the APIs
13 /// Since LLDB is constantly under active development, what you're about to
15 /// of LLDB are very stable.
/llvm-project-15.0.7/lldb/cmake/modules/
H A DLLDBFramework.cmake1 message(STATUS "LLDB.framework: build path is '${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}'")
2 message(STATUS "LLDB.framework: install path is '${LLDB_FRAMEWORK_INSTALL_DIR}'")
11 OUTPUT_NAME LLDB
18 MACOSX_FRAMEWORK_IDENTIFIER com.apple.LLDB.framework
29 OUTPUT_NAME LLDB
32 MACOSX_FRAMEWORK_IDENTIFIER com.apple.LLDB.framework
66 ${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework/Headers
67 COMMENT "LLDB.framework: create Headers symlink"
89 COMMENT "LLDB.framework: collect framework header")
104 COMMENT "LLDB.framework: copy framework headers"
[all …]
H A DLLDBConfig.cmake14 "distributed with LLDB. Please create a directory and run cmake from "
59 add_optional_dependency(LLDB_ENABLE_LIBEDIT "Enable editline support in LLDB" LibEdit LibEdit_FOUND)
61 add_optional_dependency(LLDB_ENABLE_LZMA "Enable LZMA compression support in LLDB" LibLZMA LIBLZMA_…
69 option(LLDB_BUILD_FRAMEWORK "Build LLDB.framework (Darwin only)" OFF)
77 directory containing the LLDB library.")
90 message(FATAL_ERROR "LLDB.framework can only be generated when targeting Apple platforms")
93 set(LLDB_FRAMEWORK_VERSION A CACHE STRING "LLDB.framework version (default is A)")
94 set(LLDB_FRAMEWORK_BUILD_DIR bin CACHE STRING "Output directory for LLDB.framework")
228 message(STATUS "LLDB version: ${LLDB_VERSION}")
270 # If LLDB is building against a prebuilt Clang, then the Clang resource
[all …]
/llvm-project-15.0.7/lldb/docs/resources/
H A Dcontributing.rst10 test LLDB can be found in the `build instructions <build.html>`_ and `test
13 Contributing to LLDB
18 authoring and uploading a patch. LLDB differs from the LLVM Developer
34 Error handling and use of assertions in LLDB
37 Contrary to Clang, which is typically a short-lived process, LLDB
39 debug sessions initiated by an IDE. For this reason LLDB code needs to
58 LLDB. Because assertions are not present in release builds, the
61 what allows us to refactor and evolve the LLDB code base.
63 * Logging. LLDB provides a very rich logging API. When recoverable
67 * Soft assertions. LLDB provides ``lldb_assert()`` as a soft
[all …]
H A Dbots.rst8 `add a buildbot for LLDB <https://llvm.org/docs/HowToAddABuilder.html>`_.
15 An overview of all LLDB builders can be found here:
22 GreenDragon builds and tests LLDB on macOS. It has a `dedicated tab
23 <http://green.lab.llvm.org/green/view/LLDB/>`_ for LLDB.
25 * `lldb-cmake <http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/>`_
26 * `lldb-cmake-matrix <http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-matrix/>`_
27 * `lldb-cmake-standalone <http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-standalone/>`_
28 * `lldb-cmake-sanitized <http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-sanitized/>`_
H A Dcaveats.rst12 LLDB has a powerful scripting interface which is accessible through Python.
13 Python is available either from within LLDB through a (interactive) script
17 To make this possible, LLDB links against the Python shared library. Linking
20 1. It is not possible to build and link LLDB against a Python 3 library and
23 2. It is not possible to build and link LLDB against one distribution on
29 3. To use third party Python packages from inside LLDB, you need to install
31 the one used to build and link LLDB.
34 apply to binary distributions of LLDB as well.
36 LLDB in Xcode on macOS
H A Dbuild.rst13 LLDB sources.
43 LLDB's functionality. It is strongly encouraged to build LLDB with these
83 LLDB must use debug python as well.
141 Building LLDB with CMake
185 * the main build-tree for LLDB in ``/path/to/lldb-build``
314 On macOS the LLDB test suite requires libc++. Either add
318 * ``LLDB_BUILD_FRAMEWORK:BOOL``: Builds the LLDB.framework.
361 Build LLDB standalone for development with Xcode:
413 Cross-compiling LLDB
420 LLDB on your host.
[all …]
/llvm-project-15.0.7/lldb/source/Interpreter/
H A DInterpreterProperties.td11 …Desc<"If true, LLDB will prompt you before quitting if there are any live processes being debugged…
15 Desc<"If true, LLDB will save the session's transcripts before quitting.">;
18 …Desc<"A path where LLDB will save the session's transcripts. This is particularly useful when you …
22 Desc<"If true, LLDB will stop running a 'command source' script upon encountering an error.">;
38 …Desc<"If true, LLDB will repeat the previous command if no command was passed to the interpreter. …
/llvm-project-15.0.7/lldb/tools/lldb-vscode/
H A DREADME.md47 $ rsync -av /path/to/a/built/LLDB.framework LLDB.framework
50 …LLDB.framework` inside or next to the `bin` folder depending on how the [rpath](https://en.wikiped…
85 |**initCommands** |[string]| | LLDB commands executed upon debugger startup prior to creating the…
86 |**preRunCommands** |[string]| | LLDB commands executed just before launching after the LLDB target…
87 |**stopCommands** |[string]| | LLDB commands executed just after each stop. Commands and command …
88 |**exitCommands** |[string]| | LLDB commands executed when the program exits. Commands and comman…
95 When attaching to a process using LLDB you can attach in a few ways
112 |**initCommands** |[string]| | LLDB commands executed upon debugger startup prior to creating the…
113 |**preRunCommands** |[string]| | LLDB commands executed just before launching after the LLDB target…
114 |**stopCommands** |[string]| | LLDB commands executed just after each stop. Commands and command …
[all …]
/llvm-project-15.0.7/lldb/test/Shell/ScriptInterpreter/Python/Crashlog/
H A Dparser_text.test10 …LLDB.framework (1.1000.11.38.2 - 1000.11.38.2) <96E36F5C-1A83-39A1-8713-5FDD9701C3F1> /Application…
13 # CHECK: com.apple.LLDB.framework
15 # CHECK: /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/LLDB
96 "1 com.apple.LLDB.framework 0x000000010f7954af lldb_private::HostNativeThreadBase::ThreadCr…
98 # CHECK: com.apple.LLDB.framework
/llvm-project-15.0.7/lldb/test/API/functionalities/postmortem/FreeBSDKernel/tools/
H A DREADME.rst15 3. Patch libfbsdvmcore using ``libfbsdvmcore-hacks.patch`` and build LLDB
18 4. Patch LLDB using ``lldb-minimize-processes.patch`` and build it.
20 WARNING: LLDB will now modify core files in order to make the resulting
23 5. Do a test run of ``test.script`` in LLDB against the kernel + vmcore::
27 If everything works fine, the LLDB output should be interspersed with
31 6. Open the vmcore in the patched LLDB again and choose interesting threads
/llvm-project-15.0.7/lldb/bindings/lua/
H A DCMakeLists.txt15 COMMENT "Building LLDB Lua wrapper")
32 COMMENT "LLDB Lua API")
34 set(LIBLLDB_SYMLINK_DEST "${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework/LLDB")
57 set(LLDB_LUA_INSTALL_PATH ${LLDB_FRAMEWORK_INSTALL_DIR}/LLDB.framework/Resources/Python)
/llvm-project-15.0.7/lldb/docs/status/
H A Dstatus.rst7 LLDB on FreeBSD lags behind the Linux implementation but is improving rapidly.
13 LLDB is improving on Linux. Linux is nearing feature completeness with Darwin
20 LLDB is the system debugger on macOS, iOS, tvOS, and watchOS and
25 exposed through script bridging which allows LLDB to use an embedded Python
34 LLDB is improving on NetBSD and reaching feature completeness with Linux.
39 LLDB on Windows is still under development, but already useful for i386
/llvm-project-15.0.7/lldb/
H A DCMakeLists.txt10 # If we are not building as part of LLVM, build LLDB as a standalone project,
42 "Path where Python modules are installed, relative to LLDB's install prefix")
61 "Crosscompiling LLDB with Python requires manually setting ${var}.")
79 # any source file in LLDB as the imported Clang modules might include
109 …set(lldb_python_target_dir "${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework/Resources/Python/l…
119 set(lldb_lua_target_dir "${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework/Resources/Lua")
127 option(LLDB_INCLUDE_TESTS "Generate build targets for the LLDB unit tests." ${LLVM_INCLUDE_TESTS})
H A DCODE_OWNERS.txt2 particular part of LLDB are reviewed, either by themself or by someone else.
3 They are also the gatekeepers for their part of LLDB, with the final word on
13 D: Overall LLDB architecture, Host (common+macosx), Symbol, API, ABI, Mac-specific code,
19 D: Overall LLDB architecture, Thread plans, Expression parser, ValueObject, Breakpoints, ABI
/llvm-project-15.0.7/lldb/test/API/
H A DCMakeLists.txt4 add_lit_testsuites(LLDB-API
33 …CACHE STRING "Specify the architecture to run LLDB tests as (x86|x64). Determines whether tests a…
57 …ER "${LLDB_DEFAULT_TEST_COMPILER}" CACHE PATH "C Compiler to use for building LLDB test inferiors")
61 message(FATAL_ERROR "LLDB test compiler not specified. Tests will not run.")
95 set(LLDB_FRAMEWORK_DIR ${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework)
110 … COMMENT "Copying the system debugserver to LLDB.framework's resource directory for testing.")
115 COMMENT "Copying the system debugserver to LLDB's binaries directory for testing.")
117 message(STATUS "LLDB tests use out-of-tree debugserver: ${system_debugserver_path}")
121 message(STATUS "LLDB tests use just-built debug server")
141 # LLDB uses single-config; LLVM multi-config; pick one and prefer Release types.
/llvm-project-15.0.7/lldb/test/API/commands/expression/import-std-module/module-build-errors/root/usr/include/c++/v1/
H A Dalgorithm1 // This is only defined when building, but LLDB is missing this flag when loading the standard
10 // in LLDB.
16 // Break the build when parsing from within LLDB.
/llvm-project-15.0.7/lldb/tools/intel-features/
H A DREADME.txt6 * processors from LLDB's CLI. *
14 Intel(R) architecture based processors through LLDB's command line. The library
40 while building LLDB with cmake. "cli-wrapper.cpp" file is compiled along with all
58 All CLI commands provided by this shared library can be used through the LLDB's
59 CLI by executing "plugin load <shared_lib_name>" on LLDB CLI. shared_lib_name here
/llvm-project-15.0.7/lldb/test/API/commands/expression/import-std-module/empty-module/root/usr/include/c++/v1/
H A Dalgorithm1 // This is only defined when building, but LLDB is missing this flag when loading the standard
10 // in LLDB.
17 // an empty module. Will be missing if LLDB somehow can get the
/llvm-project-15.0.7/lldb/bindings/python/
H A DCMakeLists.txt19 COMMENT "Building LLDB Python wrapper")
61 COMMENT "Python script sym-linking LLDB Python API")
135 set(LIBLLDB_SYMLINK_DEST "${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework/LLDB")
160 # Install the LLDB python module
162 …set(LLDB_PYTHON_INSTALL_PATH ${LLDB_FRAMEWORK_INSTALL_DIR}/LLDB.framework/Versions/${LLDB_FRAMEWOR…
193 COMMENT "Copying Python DLL to LLDB binaries directory.")
/llvm-project-15.0.7/lldb/test/
H A DCMakeLists.txt1 # Test runner infrastructure for LLDB. This configures the LLDB test trees
6 # llvm-lit. Because this is a standalone build, LLVM doesn't know about LLDB,
16 # build directory. LLDB queries Spotlight to locate .dSYM bundles
23 …he-lldb" CACHE PATH "The Clang module cache used by the Clang embedded in LLDB while running tests…
116 …message(WARNING "LLDB test suite requires libc++ in llvm/projects/libcxx or an existing build syml…
123 "LLDB test suite requires libc++, but it is currently disabled. "
164 message(WARNING "lld required to test LLDB on Windows")
229 # standalone LLDB build.

1234567