docs\-lldb\-html (full) in projects: llvm-project

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:docs +full:- +full:lldb +full:- +full:html (Results 1 – 25 of 49) sorted by relevance

/llvm-project/.github/workflows/
H A D	docs.yml	`4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 14 - 'main' 16 - 'llvm/docs/' 17 - 'clang/docs/' 18 - 'clan [all...]`
/llvm-project/lldb/docs/resources/
H A D	contributing.rst	5 --------------- 8 <https://llvm.org/docs/GettingStarted.html>`_ for general information on how to 10 test LLDB can be found in the `build instructions <build.html>`_ and `test 11 instructions <test.html>`_ respectively. 13 Contributing to LLDB 14 -------------------- 17 <https://llvm.org/docs/DeveloperPolicy.html>`_ for information about 18 authoring and uploading a patch. LLDB differs from the LLVM Developer 21 For anything not explicitly listed here, assume that LLDB follows the LLVM 27 LLDB's code style differs from `LLVM's coding style <https://llvm.org/docs/CodingStandards.html>`_ [all …]
H A D	fuzzing.rst	5 -------- 7 LLDB has fuzzers that provide automated `fuzz testing <https://en.wikipedia.org/wiki/Fuzzing>`_ for… 10 -------------------- 12 Building the LLDB fuzzers requires a build configuration that has the address sanitizer and sanitiz… 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… 28 $ ninja lldb-target-fuzzer [all …]
H A D	build.rst	`5 ---------- [all...]`
H A D	test.rst	`5 ---------- [all...]`
H A D	debugging.rst	4 This page details various ways to debug LLDB itself and other LLDB tools. If 5 you want to know how to use LLDB in general, please refer to 8 As LLDB is generally split into 2 tools, ``lldb`` and ``lldb-server`` 12 In this document we refer to the initial ``lldb`` as the "debugger" and the 16 ---------------------- 18 To build LLDB with debugging information add the following to your CMake 23 -DCMAKE_BUILD_TYPE=Debug \ 24 -DLLDB_EXPORT_ALL_SYMBOLS=ON 26 Note that the ``lldb`` you will use to do the debugging does not itself need to 33 configurations. This will make LLDB fail earlier instead of continuing with [all …]
H A D	extensions.rst	4 LLDB supports some DWARF extensions produced by Clang. 6 Clang ``-gmodules`` debug info 7 ------------------------------ 11 modules <https://clang.llvm.org/docs/Modules.html>`_ more efficiently. 13 From an on-disk storage perspective, Clang modules are precompiled 19 info <https://llvm.org/devmtg/2015-10/#talk19>`_. 22 ``-gmodules`` option, the precompiled header (``.pch``) or module 23 (``.pcm``) files become object file containers (on Darwin: Mach-O) 31 ``DW_TAG_module``, or -- in the case of submodules -- multiple levels 41 is used to locate external ``.dwo`` files on ELF-based platforms. The [all …]
/llvm-project/lldb/docs/
H A D	CMakeLists.txt	11 add_custom_target(lldb-cpp-doc 14 COMMENT "Generating LLDB C++ API reference with Doxygen" VERBATIM 16 set_target_properties(lldb-cpp-doc PROPERTIES FOLDER "LLDB/Docs") 26 file(MAKE_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/lldb) 28 add_custom_target(lldb-python-doc-package 29 …COMMAND "${CMAKE_COMMAND}" -E copy "${lldb_bindings_dir}/lldb.py" "${CMAKE_CURRENT_BINARY_DIR}/lld… 30 COMMAND "${CMAKE_COMMAND}" -E make_directory "${CMAKE_CURRENT_BINARY_DIR}/lldb/plugins" 31 …ND "${CMAKE_COMMAND}" -E copy "${LLDB_SOURCE_DIR}/examples/python/templates/scripted_process.py" "… 32 …ND "${CMAKE_COMMAND}" -E copy "${LLDB_SOURCE_DIR}/examples/python/templates/scripted_platform.py" … 33 …ND "${CMAKE_COMMAND}" -E copy "${LLDB_SOURCE_DIR}/examples/python/templates/operating_system.py" "… [all …]
H A D	index.rst	`1 .. 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 13 LLDB is the default debugger in Xcode on macOS and supports debugging C, 14 Objective-C and C++ on the desktop and iOS devices and simulator. 16 All of the code in the LLDB project is available under the 19 .. _"Apache 2.0 License with LLVM exceptions": https://llvm.org/docs/DeveloperPolicy.html#ne [all...]`
H A D	conf.py	`1 # -- coding: utf-8 -- 3 # LLDB documentation build configuration file, created by 4 # sphinx-quickstart on Sun Dec 9 20:01:55 2012. 17 sys.path.insert(0, os.path.abspath(os.path.join("..", "..", "llvm", "docs"))) 19 building_man_page = tags.has("builder-man") 21 # For the website we need to setup the path to the generated LLDB modul [all...]`
/llvm-project/llvm/docs/Proposals/
H A D	VariableNames.rst	12 inevitably be some details that are flawed. You can help - you can edit this 15 <http://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html>`_. 26 <../CodingStandards.html#name-types-functions-variables-and-enumerators-properly>`_ 43 The proliferation of acronyms leads to hard-to-read code such as `this 44 <https://github.com/llvm/llvm-project/blob/0a8bc14ad7f3209fe702d18e250194cd90188596/llvm/lib/Transf… 49 Many other coding guidelines [LLDB]_ [Google]_ [WebKit]_ [Qt]_ [Rust]_ [Swift]_ 61 This work-in-progress proposal is to change the coding standard for variable 65 …<https://github.com/llvm/llvm-project/blob/8b72080d4d7b13072f371712eed333f987b7a18e/llvm/lib/CodeG… 74 but here we use the terminology from clang-tidy). 77 ``lower_case`` is consistent with [LLDB]_, [Google]_, [Rust]_ and [Python]_. [all …]
/llvm-project/lldb/docs/testsuite/
H A D	a-detailed-walkthrough.txt	10 http://docs.python.org/library/unittest.html for more details. 12 To just run the TestSettings.py test, chdir to the lldb test directory, and then 15 /Volumes/data/lldb/svn/trunk/test $ ./dotest.py settings 16 ---------------------------------------------------------------------- 19 ---------------------------------------------------------------------- 23 /Volumes/data/lldb/svn/trunk/test $ 25 Pass '-v' option to the test driver to also output verbose descriptions of the 28 /Volumes/data/lldb/svn/trunk/test $ ./dotest.py -v settings 29 ---------------------------------------------------------------------- 33 Test that after 'set auto-confirm true', manual confirmation should not kick in. ... ok [all …]
/llvm-project/clang/www/
H A D	hacking.html	`1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" 3 <!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ --> 4 <html> 6 <META http-equi [all...]`
H A D	get_involved.html	1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" 3 <html> 5 <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> 6 <title>Clang - Get Involved</title> 12 <!--#include virtual="menu.html.incl"--> 18 <p>Once you have <a href="get_started.html">checked out and built</a> clang and 26 See the <a href="hacking.html">hacking</a> document for information on how 35 <li><a href="https://discourse.llvm.org/c/clang/6">Clang Frontend Discourse forum</a> - 39 <li><a href="https://discord.gg/xS7Z362">Discord chat</a> - Real-time chat for 45 standards-related activities happening within the Clang community. These [all …]
/llvm-project/llvm/docs/CommandGuide/
H A D	tblgen.rst	1 tblgen - Description to C++ Code 7 -------- 9 :program:`clang-tblge [all...]
/llvm-project/llvm/docs/
H A D	ReleaseNotes.rst
H A D	CMake.rst	11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake 34 We use here the command-line, non-interactive CMake interface. 36 #. `Download <http://www.cmake.org/cmake/resources/software.html>`_ and install 45 .. code-block:: console 53 .. code-block:: console 70 components are built; see the `Frequently Used LLVM-related 76 .. code-block:: console 78 $ cmake - [all...]
H A D	GettingInvolved.rst	`31 The LLVM project's code-review process. 34 The LLVM support policy for core and non-core components. 52 Describes how to use the llvm-project repository and code reviews on GitHub. 60 .. _development-process: 63 ------ [all...]`
H A D	MeetupGuidelines.rst	10 `Code of Conduct <https://llvm.org/docs/CodeOfConduct.html>`_. 12 Other than that - your mileage may vary. Please adapt your social to what works 16 ------- [all...]
/llvm-project/openmp/docs/
H A D	conf.py	1 # -- coding: utf-8 -- 3 # LLDB documentation build configuration file, created by 4 # sphinx-quickstart on Sun Dec 9 20:01:55 2012. 22 # -- General configuration ----------------------------------------------------- 38 # source_encoding = 'utf-8-sig' 45 copyright = "2013-%d, LLVM/OpenMP" % date.today().year 63 # non-false value, then it is used: 75 # If true, '()' will be appended to :func: etc. cross-reference text. 93 # -- Options for HTML output --------------------------------------------------- 95 # The theme to use for HTML and HTML Help pages. See the documentation for [all …]
/llvm-project/lldb/include/lldb/Utility/
H A D	TraceIntelPTGDBRemotePackets.h	1 //===-- TraceIntelPTGDBRemotePackets.h --------------------------- C++ --===// 5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 //===----------------------------------------------------------------------===// 12 #include "lldb/Utility/TraceGDBRemotePackets.h" 19 /// See docs/lldb-gdb-remote.txt for more information. 21 /// Do not use system-dependent types, like size_t, because they might cause 32 /// jLLDBTraceStart gdb-remote packet 82 /// jLLDBTraceGetState gdb-remote packet 88 /// https://man7.org/linux/man-pages/man2/perf_event_open.2.html for more 96 /// https://man7.org/linux/man-pages/man2/perf_event_open.2.html
/llvm-project/lldb/
H A D	.gitignore	3 # See: http://www.kernel.org/pub/software/scm/git/docs/gitignore.html 5 # This file is intentionally different from the output of `git svn show-ignore`, 20 .python-version 32 .remote-build.conf 36 llvm-build/ 42 clang-module-cache 44 # Skip ctags-style tags files 47 # We should ignore Xcode-style embedding of llvm/ at lldb root dir. 53 20??-??-??-??_??_??/
/llvm-project/
H A D	.gitignore	3 # See: http://www.kernel.org/pub/software/scm/git/docs/gitignore.html 5 # This file is intentionally different from the output of `git svn show-ignore`, 50 # Visual Studio built-in CMake configuration 54 /cmake-build* 75 /lldb/docs/python_api/
/llvm-project/lldb/packages/Python/lldbsuite/test/
H A D	README-TestSuite	1 This README file describes the files and directories related -- rst -- 4 - dotest.py 7 directory and issue the './dotest.py' command or './dotest.py -v' for more 8 verbose output. '.dotest.py -h' prints out the help messge. 16 1. ./dotest.py -v . 2> ~/Developer/Log/lldbtest.log0 19 …2. LLDB_LOG=/tmp/lldb.log GDB_REMOTE_LOG=/tmp/gdb-remote.log ./dotest.py -v . 2> ~/Developer/Log/l… 20 This runs the test suite, with logging turned on for the lldb as well as 21 the process.gdb-remote channels and directs the run log to a file. 23 - lldbtest.py 25 Provides an abstract base class of lldb test case named 'TestBase', which in [all …]
/llvm-project/lldb/docs/use/
H A D	intel_pt.rst	6 LLDB can collect traces and dump them using its symbolication stack. 8 https://easyperf.net/blog/2019/08/23/Intel-Processor-Trace. 11 ------------- 14 (see https://www.intel.com/content/www/us/en/support/articles/000056730/processors.html) 27 ------------------ 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`` 40 and ``<libipt-build>/libipt/include`` directories. [all …]