Home
last modified time | relevance | path

Searched +full:lldb +full:- +full:build (Results 1 – 25 of 994) sorted by relevance

12345678910>>...40

/llvm-project/lldb/docs/resources/
H A Dbuild.rst5 ----------
[all...]
H A Dfuzzing.rst5 --------
7 LLDB has fuzzers that provide automated `fuzz testing <https://en.wikipedia.org/wiki/Fuzzing>`_ for…
10 --------------------
12 …LLDB fuzzers requires a build configuration that has the address sanitizer and sanitizer coverage …
16 -DLLVM_USE_SANITIZER='Address' \
17 -DLLVM_USE_SANITIZE_COVERAGE=On \
18 -DCLANG_ENABLE_PROTO_FUZZER=ON
20 …zzer's sanitizer coverage is available here: `<https://llvm.org/docs/LibFuzzer.html#fuzzer-usage>`_
22 If you want to debug LLDB itself when you find a bug using the fuzzers, use the CMake option ``-DCM…
24 To build a fuzzer, run the desired ninja command for the fuzzer(s) you want to build:
[all …]
H A Dcaveats.rst7 ------
9 LLDB has a powerful scripting interface which is accessible through Python.
10 Python is available either from within LLDB through a (interactive) script
14 To make this possible, LLDB links against the Python shared library. Linking
17 1. It is not possible to build and link LLDB against a Python 3 library and
20 2. It is not possible to build and link LLDB against one distribution on
22 For example, on macOS, if you build and link against Python from
23 python.org, you cannot import the lldb module from the Python interpreter
26 3. To use third party Python packages from inside LLDB, you need to install
28 the one used to build and link LLDB.
[all …]
/llvm-project/llvm/utils/gn/secondary/lldb/test/
H A DBUILD.gn3 #import("//llvm/utils/gn/build/libs/xar/enable.gni")
4 import("//llvm/utils/gn/build/libs/xml/enable.gni")
5 import("//llvm/utils/gn/build/libs/zlib/enable.gni")
6 import("//llvm/utils/gn/build/write_cmake_config.gni")
18 rebase_path(get_label_info("//lldb", "target_out_dir")),
19 "LLDB_SOURCE_DIR=" + rebase_path("//lldb"),
23 "LLVM_LIT_TOOLS_DIR=", # Intentionally empty, matches cmake build.
33 write_cmake_config("lit-lldb-ini
[all...]
/llvm-project/lldb/test/
H A DCMakeLists.txt1 # Test runner infrastructure for LLDB. This configures the LLDB test trees
7 "LLDB test suite requires a Python3 interpreter but none "
13 message(STATUS "Enforcing strict test requirements for LLDB")
14 # Lit uses psutil to do per-test timeouts.
35 # In order to run check-lldb-* we need the correct map_config directives in
36 # llvm-lit. Because this is a standalone build, LLV
[all...]
/llvm-project/.github/workflows/
H A Ddocs.yml4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
6 name: "Test documentation build"
14 - 'main'
16 - 'llvm/docs/**'
17 - 'clang/docs/**'
18 - 'clang/include/clang/Basic/AttrDocs.td'
19 - 'clan
[all...]
/llvm-project/lldb/docs/use/
H A Dqemu-testing.rst
H A Dintel_pt.rst6 LLDB can collect traces and dump them using its symbolication stack.
8 https://easyperf.net/blog/2019/08/23/Intel-Processor-Trace.
11 -------------
26 Build Instructions
27 ------------------
29 Clone and build the low level Intel PT
34 $ mkdir libipt-build
35 $ cmake -S libipt -B libipt-build
36 $ cd libipt-build
39 This will generate a few files in the ``<libipt-build>/lib``
[all …]
H A Dtroubleshooting.rst5 ---------------------------------------------
8 information. Typically this means passing -g to the compiler when compiling
12 etc), LLDB by default will only search for compile units whose filename
24 "foo.c". If your code does this, or if your build system combines multiple
26 compiled into another implementation file, you will need to tell LLDB to always
32 $ echo "settings set target.inline-breakpoint-strategy always" >> ~/.lldbinit
34 This tells LLDB to always look in all compile units and search for breakpoint
49 If you are using an IDE and you move your project in your file system and build
50 again, sometimes doing a clean then build will solve the issue.This will fix
52 the build folder might still contain stale debug information with the old
[all …]
/llvm-project/lldb/cmake/modules/
H A DLLDBConfig.cmake14 "In-source builds are not allowed. CMake would overwrite the makefiles "
15 "distributed with LLDB. Please create a directory and run cmake from "
54 add_optional_dependency(LLDB_ENABLE_SWIG "Enable SWIG to generate LLDB bindings" SWIG SWIG_FOUND VERSION 4)
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 CURSESANDPANEL_FOUND)
57 add_optional_dependency(LLDB_ENABLE_LZMA "Enable LZMA compression support in LLDB" LibLZMA LIBLZMA_FOUND)
58 add_optional_dependency(LLDB_ENABLE_LUA "Enable Lua scripting support in LLDB" LuaAndSwig LUAANDSWIG_FOUND)
59 add_optional_dependency(LLDB_ENABLE_PYTHON "Enable Python scripting support in LLDB" PythonAndSwig PYTHONANDSWIG_FOUND)
60 add_optional_dependency(LLDB_ENABLE_LIBXML2 "Enable Libxml 2 support in LLDB" LibXml2 LIBXML2_FOUND VERSION 2.8)
61 add_optional_dependency(LLDB_ENABLE_FBSDVMCORE "Enable libfbsdvmcore support in LLDB" FBSDVMCor
[all...]
/llvm-project/lldb/test/API/commands/dwim-print/
H A DTestDWIMPrint.py2 Test dwim-print with variables, variable paths, and expressions.
6 import lldb
13 def _run_cmd(self, cmd: str) -> str:
14 """Run the given lldb command and return its output."""
15 result = lldb.SBCommandReturnObject()
21 def _strip_result_var(self, string: str) -> str:
26 compare it to `dwim-print` output, which disables result variables.
34 ) -> None:
35 """Run dwim-print and verify the output against the expected command."""
36 # Resolve the dwim-prin
[all...]
/llvm-project/lldb/test/API/python_api/target/
H A DTestTargetAPI.py6 import lldb
34 self.build(dictionary=d)
41 self.build(dictionary=d)
49 self.build(dictionary=d)
55 self.build()
61 self.build()
66 self.build(dictionary=d)
74 self.build(dictionary=d)
81 self.build(dictionary=d)
88 self.build(dictionar
[all...]
/llvm-project/llvm/utils/gn/secondary/lldb/tools/driver/
H A DBUILD.gn3 import("//llvm/utils/gn/build/toolchain/compiler.gni")
4 import("//llvm/utils/gn/build/write_cmake_config.gni")
8 visibility = [ ":lldb" ]
9 args = [ "-gen-opt-parser-defs" ]
14 input = "lldb-Info.plist.in"
15 output = "$target_gen_dir/lldb-Info.plist"
22 executable("lldb") {
23 configs += [ "//llvm/utils/gn/build:lldb_code" ]
26 "//lldb/include/lldb/Host:Config",
27 "//lldb/source/API:liblldb",
[all …]
/llvm-project/lldb/test/Shell/Minidump/
H A Dfb-dump.test1 # RUN: yaml2obj %s -o %t
2 # RUN: %lldb -c %t -o 'process plugin dump --all' | \
3 # RUN: FileCheck --check-prefix=CHECK-DIR --check-prefix=CHECK-APPDATA \
4 # RUN: --check-prefix=CHECK-BUILD --check-prefix=CHECK-VERSION \
5 # RUN: --check-prefix=CHECK-JAVA --check-prefix=CHECK-DALVIK \
6 # RUN: --check-prefix=CHECK-UNWIND --check-prefix=CHECK-ERROR \
7 # RUN: --check-prefix=CHECK-APPSTATE --check-prefix=CHECK-ABORT \
8 # RUN: --check-prefix=CHECK-THREAD --check-prefix=CHECK-LOGCAT %s
9 # RUN: %lldb -c %t -o 'process plugin dump -a' | \
10 # RUN: FileCheck --check-prefix=CHECK-DIR --check-prefix=CHECK-APPDATA \
[all …]
/llvm-project/lldb/test/API/python_api/thread/
H A DTestThreadAPI.py5 import lldb
15 self.build()
20 self.build()
25 # We build a different executable than the default build() does.
27 self.build(dictionary=d)
36 # We build a different executable than the default build() does.
38 self.build(dictionary=d)
44 # We build
[all...]
/llvm-project/lldb/test/API/functionalities/breakpoint/hardware_breakpoints/require_hw_breakpoints/
H A DTestRequireHWBreakpoints.py9 import lldb
20 self.build()
24 self.runCmd("settings set target.require-hardware-breakpoint true")
32 self.build()
35 self, lldb.SBFileSpec("main.c"), 1
38 self.runCmd("settings set target.require-hardware-breakpoint true")
41 self.expect("thread step-in")
42 self.expect("thread step-in", error=True)
45 error = lldb.SBError()
55 self.build()
[all …]
/llvm-project/lldb/test/API/functionalities/completion/
H A DTestCompletion.py2 Test the lldb command line completion mechanism.
8 import lldb
36 self.build()
39 self, "// Break here", lldb.SBFileSpec("main.cpp")
41 self.assertState(process.GetState(), lldb.eStateStopped)
49 self.build()
52 self, "// Break here", lldb.SBFileSpec("main.cpp")
54 self.assertState(process.GetState(), lldb.eStateStopped)
59 self.do_test_variable_completion("dwim-print")
67 self.complete_from_to(f"{command} ptr_fooo->",
[all...]
/llvm-project/lldb/test/API/commands/frame/var/
H A DTestFrameVar.py2 Make sure the frame variable -g, -a, and -l flags work.
6 import lldb
22 self.build()
31 "Set a breakpoint here", lldb.SBFileSpec("main.c")
37 error = lldb.SBError()
58 command_result = lldb.SBCommandReturnObject()
61 # Ensure --rege
[all...]
/llvm-project/lldb/test/API/functionalities/jitloader_gdb/
H A DTestJITLoaderGDB.py6 import lldb
20 self.build()
33 self.assertState(process.GetState(), lldb.eStateExited)
38 "jitintgdb-{}.txt".format(self.getArchitecture())
50 "settings show plugin.jit-loader.gdb.enable",
51 substrs=["plugin.jit-loader.gdb.enable (enum) = default"],
54 @skipIfWindows # This test fails on Windows during C code build
57 self.build()
61 self.runCmd("log enable -f %s lldb jit" % (logfile))
62 self.runCmd("settings set plugin.jit-loader.gdb.enable on")
[all …]
/llvm-project/lldb/test/API/lang/cpp/static_members/
H A DTestCPPStaticMembers.py6 import lldb
16 self.build()
18 self, "// stop in main", lldb.SBFileSpec("main.cpp")
28 self.build()
30 self, "// stop in member function", lldb.SBFileSpec("main.cpp")
39 self.build()
51 Test that LLDB doesn't crash on evaluating specific expression involving
55 self.build()
57 self, "// stop in main", lldb.SBFileSpec("main.cpp")
64 # The IR interpreter doesn't support non-const operands to the
[all …]
/llvm-project/lldb/
H A DCMakeLists.txt2 set(LLVM_SUBPROJECT_TITLE "LLDB")
17 # If we are not building as part of LLVM, build LLDB as a standalone project,
20 project(lldb) project
28 option(LLDB_INCLUDE_TESTS "Generate build targets for the LLDB unit tests." ${LLVM_INCLUDE_TESTS})
41 # Define the LLDB_CONFIGURATION_xxx matching the build type.
43 add_definitions(-DLLDB_CONFIGURATION_DEBUG)
47 add_definitions(-D_ENABLE_EXTENDED_ALIGNED_STORAGE)
50 add_definitions(-D_BSD_SOURC
[all...]
/llvm-project/lldb/test/API/commands/command/backticks/
H A DTestBackticksInAlias.py6 import lldb
16 self.build()
18 self, "break here", lldb.SBFileSpec("main.c")
21 result = lldb.SBCommandReturnObject()
23 "command alias _test-argv-cmd expression -Z \`argc\` -- argv", result
26 interp.HandleCommand("_test-argv-cmd", result)
31 "command alias _test-argv-parray-cmd parray \`argc\` argv", result
34 interp.HandleCommand("_test-argv-parray-cmd", result)
43 self.build()
45 self, "break here", lldb.SBFileSpec("main.c")
[all …]
/llvm-project/lldb/test/API/functionalities/breakpoint/serialize/
H A DTestBreakpointSerialization.py7 import lldb
19 self.build()
25 self.build()
31 self.build()
37 self.build()
43 self.build()
48 self.build()
54 self.build()
78 stream = lldb.SBStream()
93 result = lldb.SBCommandReturnObject()
[all …]
/llvm-project/lldb/test/API/lang/cpp/namespace/
H A DTestNamespaceLookup.py7 import lldb
44 @unittest.expectedFailure # CU-local objects incorrectly scoped
46 """Test scope lookup of functions in lldb."""
47 self.build()
50 self, self.line_break_global_scope, lldb.SBFileSpec("ns.cpp")
72 # FIXME: LLDB does not correctly scope CU-local objects.
73 # LLDB currently lumps functions from all files into
75 # functions are considered, LLDB can incorrectly call
79 # Evaluate func() - shoul
[all...]
/llvm-project/lldb/packages/Python/lldbsuite/test/
H A Ddotest_args.py7 # LLDB modules
13 description="description", prefix_chars="+-", add_help=False
25 "-h",
26 "--help",
29 help="Print this help message and exit. Add '-v' for more detailed help.",
35 "-A",
36 "--arch",
44 "-C",
45 "--compiler",
49 …"""Specify the compiler(s) used to build the inferior executables. The compiler path can be an exe…
[all …]

12345678910>>...40