Home
last modified time | relevance | path

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

1234567

/external/llvm-project/lldb/docs/use/
Dlinks.md4 This page contains links to external resources on how to use LLDB. Being listed
9 ### [Dancing in the Debugger — A Waltz with LLDB (2014) ](https://www.objc.io/issues/19-debugging/l…
11 A high level overview of LLDB with a focus on debugging Objective-C code.
15 ### [LLDB: Beyond "po" (2019)](https://developer.apple.com/videos/play/wwdc2019/429/)
17 LLDB is a powerful tool for exploring and debugging your app at runtime.
19 data types, and how to extend LLDB using your own Python 3 scripts.
21 ### [Advanced Debugging with Xcode and LLDB (2018)](https://developer.apple.com/videos/play/wwdc201…
24 debugging workflows. Learn how to take advantage of LLDB and custom breakpoints
28 ### [Debugging with LLDB (2012)](https://developer.apple.com/videos/play/wwdc2012/415/)
30 LLDB is the next-generation debugger for macOS and iOS. Get an introduction to
[all …]
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
21 as to how variables should be displayed. The LLDB type command allows you to do
46 printed, LLDB will first check if custom printing options have been associated
72 at the LLDB command line.
114 This is because by default LLDB cascades formats through typedef chains. In
135 and --skip-references (-r). These two options prevent LLDB from applying a
180 | ``default`` | | the default LLDB algorithm is …
300 processed by LLDB to generate the summary.
367 ``${*var`` tells LLDB to get the object that the expression paths leads to, and
[all …]
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
/external/llvm-project/lldb/docs/
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
25 with GDB there is a cheat sheet listing common tasks and their LLDB equivalent
26 in the `GDB to LLDB command map <https://lldb.llvm.org/use/map.html>`_.
[all …]
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.
/external/llvm-project/lldb/cmake/modules/
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}'")
3 message(STATUS "LLDB.framework: resources subdirectory is 'Versions/${LLDB_FRAMEWORK_VERSION}/Resou…
11 OUTPUT_NAME LLDB
18 MACOSX_FRAMEWORK_IDENTIFIER com.apple.LLDB.framework
21 MACOSX_FRAMEWORK_INFO_PLIST ${LLDB_SOURCE_DIR}/resources/LLDB-Info.plist.in
29 OUTPUT_NAME LLDB
32 MACOSX_FRAMEWORK_IDENTIFIER com.apple.LLDB.framework
35 MACOSX_FRAMEWORK_INFO_PLIST ${LLDB_SOURCE_DIR}/resources/LLDB-Info.plist.in
66 ${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework/Headers
[all …]
DLLDBConfig.cmake14 "distributed with LLDB. Please create a directory and run cmake from "
55 add_optional_dependency(LLDB_ENABLE_LIBEDIT "Enable editline support in LLDB" LibEdit LibEdit_FOUND)
56 add_optional_dependency(LLDB_ENABLE_CURSES "Enable curses support in LLDB" CursesAndPanel CURSESAND…
57 add_optional_dependency(LLDB_ENABLE_LZMA "Enable LZMA compression support in LLDB" LibLZMA LIBLZMA_…
58 add_optional_dependency(LLDB_ENABLE_LUA "Enable Lua scripting support in LLDB" LuaAndSwig LUAANDSWI…
59 add_optional_dependency(LLDB_ENABLE_PYTHON "Enable Python scripting support in LLDB" PythonAndSwig …
60 add_optional_dependency(LLDB_ENABLE_LIBXML2 "Enable Libxml 2 support in LLDB" LibXml2 LIBXML2_FOUND…
64 option(LLDB_BUILD_FRAMEWORK "Build LLDB.framework (Darwin only)" OFF)
80 message(FATAL_ERROR "LLDB.framework can only be generated when targeting Apple platforms")
83 set(LLDB_FRAMEWORK_VERSION A CACHE STRING "LLDB.framework version (default is A)")
[all …]
/external/llvm-project/lldb/docs/resources/
Dbots.rst8 `add a buildbot for LLDB <https://llvm.org/docs/HowToAddABuilder.html>`_.
16 An overview of all LLDB builders can be found here:
23 GreenDragon builds and tests LLDB on macOS. It has a `dedicated tab
24 <http://green.lab.llvm.org/green/view/LLDB/>`_ for LLDB.
26 * `lldb-cmake <http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/>`_
27 * `lldb-cmake-matrix <http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-matrix/>`_
28 * `lldb-cmake-reproducers <http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-reproducers/>`_
29 * `lldb-cmake-standalone <http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-standalone/>`_
30 * `lldb-cmake-sanitized <http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-sanitized/>`_
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
22 patches, but note that LLDB uses a different system for tests. Refer to the
26 - **Coding Style**: LLDB's code style differs from LLVM's coding style.
30 For anything not explicitly listed here, assume that LLDB follows the LLVM
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
[all …]
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
Dbuild.rst13 LLDB sources.
20 LLDB relies on many of the technologies developed by the larger LLVM project.
33 If you want to run the test suite, you'll need to build LLDB with Python
43 LLDB's functionality. It is strongly encouraged to build LLDB with these
81 and swig versions older than 4.0.0 which makes builds of LLDB using debug
83 LLDB must use debug python as well.
120 Any command prompt from which you build LLDB should have a valid Visual Studio
130 * If you are building both Clang and LLDB together, be sure to also check out
133 Building LLDB with CMake
137 its subprojects. This is the recommended way to build LLDB. Check out the
[all …]
/external/llvm-project/lldb/tools/lldb-vscode/
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…
89 |**terminateCommands** |[string]| | LLDB commands executed when the debugging session ends. Command…
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…
[all …]
/external/llvm-project/lldb/test/Shell/ScriptInterpreter/Python/Crashlog/
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
/external/llvm/test/DebugInfo/X86/
Ddebugger-tune.ll4 ; and the apple_names section to distinguish the LLDB case. SCE has neither.
8 …_64-apple-darwin12 -filetype=obj < %s | llvm-readobj -sections - | FileCheck --check-prefix=LLDB %s
14 …filetype=obj -debugger-tune=lldb < %s | llvm-readobj -sections - | FileCheck --check-prefix=LLDB %s
22 ; LLDB-NOT: debug_pubnames
23 ; LLDB: apple_names
24 ; LLDB-NOT: debug_pubnames
/external/llvm-project/lldb/docs/status/
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
/external/llvm-project/lldb/test/API/
DCMakeLists.txt26 …CACHE STRING "Specify the architecture to run LLDB tests as (x86|x64). Determines whether tests a…
34 # build directory. LLDB queries Spotlight to locate .dSYM bundles
58 …ER "${LLDB_DEFAULT_TEST_COMPILER}" CACHE PATH "C Compiler to use for building LLDB test inferiors")
64 message(FATAL_ERROR "LLDB test compiler not specified. Tests will not run.")
98 set(LLDB_FRAMEWORK_DIR ${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework)
112 COMMENT "Copying the system debugserver to LLDB's binaries directory for testing.")
113 message(STATUS "LLDB tests use out-of-tree debugserver: ${system_debugserver_path}")
118 message(STATUS "LLDB Tests use just-built debugserver: ${debugserver_path}")
123 message(STATUS "LLDB Tests use just-built lldb-server: ${lldb_server_path}")
127 message(WARNING "LLDB Tests enabled, but no server available")
[all …]
/external/llvm-project/lldb/source/Interpreter/
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.">;
19 Desc<"If true, LLDB will stop running a 'command source' script upon encountering an error.">;
/external/llvm-project/lldb/tools/intel-features/intel-pt/
DREADME_TOOL.txt14 The Intel(R) Processor Trace Tool is developed on top of LLDB and provides its
16 Intel(R) Processor Trace hardware feature implementation inside LLDB for this
33 1. Raw Trace Collection from LLDB
35 can be started on the application being debugged with LLDB. The generated
36 trace of the application is gathered inside LLDB and is collected by the
37 Tool from LLDB through LLDB's public API.
44 information from LLDB public API and provide it to "libipt". More
63 raw trace of an application from LLDB. This hardware feature may not be
71 machine where the application is running and being debugged by LLDB. This
89 while building LLDB with cmake. The following cmake flags need to be provided to
[all …]
/external/llvm-project/lldb/test/
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,
18 …he-lldb" CACHE PATH "The Clang module cache used by the Clang embedded in LLDB while running tests…
104 …message(WARNING "LLDB test suite requires libc++ in llvm/projects/libcxx or an existing build syml…
114 "LLDB test suite requires libc++, but it is currently disabled. "
120 "LLDB test suite requires libc++, but it is currently disabled. "
153 message(WARNING "lld required to test LLDB on Windows")
183 add_lit_testsuites(LLDB
245 # standalone LLDB build.
/external/llvm-project/lldb/test/API/commands/expression/import-std-module/empty-module/root/usr/include/c++/v1/
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
/external/llvm-project/lldb/tools/intel-features/
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
63 All CLI commands provided by this shared library can be used through the LLDB's
64 CLI by executing "plugin load <shared_lib_name>" on LLDB CLI. shared_lib_name here
/external/llvm-project/lldb/
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
/external/llvm-project/debuginfo-tests/dexter/dex/debugger/lldb/
D__init__.py8 from dex.debugger.lldb.LLDB import LLDB
/external/llvm-project/lldb/bindings/python/
DCMakeLists.txt18 COMMENT "Building LLDB Python wrapper")
62 COMMENT "Python script sym-linking LLDB Python API")
128 set(LIBLLDB_SYMLINK_DEST "${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework/LLDB")
156 # Install the LLDB python module
158 set(LLDB_PYTHON_INSTALL_PATH ${LLDB_FRAMEWORK_INSTALL_DIR}/LLDB.framework/Resources/Python)
189 COMMENT "Copying Python DLL to LLDB binaries directory.")
/external/llvm-project/lldb/test/Unit/
DREADME.md1 # LLDB Unit Tests
4 the `unittest` directory in top level LLDB directory.

1234567