Home
last modified time | relevance | path

Searched +full:docs +full:- +full:lldb +full:- +full:man (Results 1 – 14 of 14) sorted by relevance

/llvm-project/.github/workflows/
H A Ddocs.yml4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
14 - 'main'
16 - 'llvm/docs/**'
17 - 'clang/docs/**'
18 - 'clan
[all...]
/llvm-project/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
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#new-llv
[all...]
H A Dconf.py1 # -*- 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")
[all...]
H A DCMakeLists.txt11 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 Ddoxygen.cfg.in13 #---------------------------------------------------------------------------
15 #---------------------------------------------------------------------------
18 # that follow. The default is UTF-8 which is also the encoding used for all
23 DOXYFILE_ENCODING = UTF-8
28 PROJECT_NAME = LLDB
41 OUTPUT_DIRECTORY = @abs_top_builddir@/docs/cpp_reference
44 # 4096 sub-directories (in 2 levels) under the output directory of each output
56 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
58 # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
59 # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
[all …]
/llvm-project/lldb/test/Shell/Driver/
H A DTestHelp.test1 RUN: %lldb --help | FileCheck %s
2 RUN: cat %S/../../../docs/man/lldb.rst | FileCheck %s
5 CHECK: --attach-name
6 CHECK: -
[all...]
/llvm-project/lldb/include/lldb/Utility/
H A DTraceIntelPTGDBRemotePackets.h1 //===-- 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/tools/driver/
H A DOptions.td3 class F<string name>: Flag<["--", "-"], name>;
4 class S<string name>: Separate<["--", "-"], name>;
8 // Please keep this in sync with the man page in docs/man/lldb.rst
13 def attach_name: Separate<["--", "-"], "attach-name">,
17 def: Separate<["-"], "n">,
19 HelpText<"Alias for --attach-name">,
22 def wait_for: F<"wait-for">,
25 def: Flag<["-"], "w">,
27 HelpText<"Alias for --wait-for">,
30 def attach_pid: Separate<["--", "-"], "attach-pid">,
[all …]
/llvm-project/lldb/docs/resources/
H A Dbuild.rst5 ----------
[all...]
H A Ddebugging.rst4 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 Dlldbgdbremote.md3 LLDB has added new GDB server packets to better support multi-threaded and
5 [protocol defined by GDB ](https://sourceware.org/gdb/current/onlinedocs/gdb.html/Packets.html#Packets) (and [this page](https://sourceware.org/gdb/current/onlinedocs/gdb.html/Host-I_002fO-Packets.html#Host-I_002fO-Packets) for `vFile` packets).
7 If a packet is restated here it is because LLDB's version has some behaviour
8 difference to GDB's version, or it provides some context for a following LLDB
13 mismatch, then things go wrong very quickly. LLDB makes extensive use of the GDB
23 registers a thread might have. Again with GDB, both sides pre-agre
[all...]
/llvm-project/openmp/docs/
H A Dconf.py1 # -*- 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 ---------------------------------------------------
97 html_theme = "llvm-openmp-theme"
[all …]
/llvm-project/llvm/docs/
H A DCMake.rst11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
34 We use here the command-line, non-interactive CMake interface.
45 .. code-block:: console
53 .. code-block:: console
70 components are built; see the `Frequently Used LLVM-related
76 .. code-block:: console
78 $ cmake --buil
[all...]
/llvm-project/llvm/docs/Proposals/
H A DGitHubMove.rst22 infrastructure) will continue to work with a Git-based LLVM.
29 This proposal relates only to moving the hosting of our source-code repository
31 using GitHub's issue tracker, pull-requests, or code-review.
35 username/password-hash.
41 ----------------
57 --------
66 through the Git-SVN integration.
82 -----------
85 projects. Any of these could replace the code-hosting infrastructure that we
92 BitBucket: it offers read-write **SVN** access to the repository
[all …]