| /dports/devel/llvm-devel/llvm-project-f05c95f10fc1d8171071735af8ad3a9e87633120/lldb/docs/use/ |
| H A D | variable.rst | 7 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
72 at the LLDB command line.
149 and --skip-references (-r). These two options prevent LLDB from applying a
314 processed by LLDB to generate the summary.
622 LLDB to detect the end of the pointed data.
902 including it in the range of children displayed by LLDB. For example,
942 children provider in LLDB:
1065 compiled into the LLDB core).
[all …]
|
| H A D | qemu-testing.rst | 1 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
|
| /dports/devel/wasi-compiler-rt13/llvm-project-13.0.1.src/lldb/docs/use/ |
| H A D | variable.rst | 7 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
72 at the LLDB command line.
149 and --skip-references (-r). These two options prevent LLDB from applying a
314 processed by LLDB to generate the summary.
622 LLDB to detect the end of the pointed data.
902 including it in the range of children displayed by LLDB. For example,
942 children provider in LLDB:
1065 compiled into the LLDB core).
[all …]
|
| H A D | qemu-testing.rst | 1 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
|
| /dports/devel/wasi-compiler-rt12/llvm-project-12.0.1.src/lldb/docs/use/ |
| H A D | variable.rst | 7 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
72 at the LLDB command line.
135 and --skip-references (-r). These two options prevent LLDB from applying a
300 processed by LLDB to generate the summary.
608 LLDB to detect the end of the pointed data.
888 including it in the range of children displayed by LLDB. For example,
928 children provider in LLDB:
1051 compiled into the LLDB core).
[all …]
|
| H A D | qemu-testing.rst | 1 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
|
| /dports/devel/llvm13/llvm-project-13.0.1.src/lldb/docs/use/ |
| H A D | variable.rst | 7 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
72 at the LLDB command line.
149 and --skip-references (-r). These two options prevent LLDB from applying a
314 processed by LLDB to generate the summary.
622 LLDB to detect the end of the pointed data.
902 including it in the range of children displayed by LLDB. For example,
942 children provider in LLDB:
1065 compiled into the LLDB core).
[all …]
|
| H A D | qemu-testing.rst | 1 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
|
| /dports/devel/tinygo/tinygo-0.14.1/llvm-project/lldb/docs/status/ |
| H A D | status.rst | 7 LLDB is the system debugger on macOS, iOS, tvOS, and watchOS and
12 exposed through script bridging which allows LLDB to use an embedded Python
21 LLDB is improving on Linux. While the debugserver has not been ported (to
30 LLDB on FreeBSD lags behind the Linux implementation but is improving rapidly.
36 LLDB on Windows is still under development, but already useful for i386
|
| /dports/devel/tinygo/tinygo-0.14.1/llvm-project/lldb/docs/use/ |
| H A D | variable.rst | 7 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
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
300 processed by LLDB to generate the summary.
607 LLDB to detect the end of the pointed data.
908 children provider in LLDB:
1031 compiled into the LLDB core).
[all …]
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/lldb/docs/use/ |
| H A D | qemu-testing.rst | 1 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
125 …s compile LLDB server for AArch64 Linux: Please visit https://lldb.llvm.org/resources/build.html f…
127 * Transfer LLDB server executable to emulation environment
|
| /dports/devel/wasi-libcxx/llvm-project-13.0.1.src/lldb/docs/use/ |
| H A D | qemu-testing.rst | 1 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
|
| /dports/devel/kdevelop/kdevelop-21.12.3/po/ja/ |
| H A D | kdevlldb.po | 24 msgid "LLDB"
30 msgid "LLDB Console"
35 msgid "Attempting to execute user command on unsupported LLDB version"
66 msgid "LLDB Version Unsupported"
72 "<b>You need lldb-mi from LLDB 3.8.1 or higher.</b><br />You are using: %1"
83 msgid "Debug a native application in LLDB"
96 msgid "LLDB Configuration"
180 msgid "LLDB Console"
|
| /dports/devel/kdevelop/kdevelop-21.12.3/po/lt/ |
| H A D | kdevlldb.po | 28 msgid "LLDB"
34 msgid "LLDB Console"
39 msgid "Attempting to execute user command on unsupported LLDB version"
70 msgid "LLDB Version Unsupported"
76 "<b>You need lldb-mi from LLDB 3.8.1 or higher.</b><br />You are using: %1"
87 msgid "Debug a native application in LLDB"
100 msgid "LLDB Configuration"
184 msgid "LLDB Console"
|
| /dports/devel/kdevelop/kdevelop-21.12.3/po/zh_TW/ |
| H A D | kdevlldb.po | 28 msgid "LLDB"
34 msgid "LLDB Console"
39 msgid "Attempting to execute user command on unsupported LLDB version"
70 msgid "LLDB Version Unsupported"
76 "<b>You need lldb-mi from LLDB 3.8.1 or higher.</b><br />You are using: %1"
87 msgid "Debug a native application in LLDB"
100 msgid "LLDB Configuration"
184 msgid "LLDB Console"
|
| /dports/devel/llvm12/llvm-project-12.0.1.src/lldb/docs/use/ |
| H A D | qemu-testing.rst | 1 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
|
| /dports/lang/rust/rustc-1.58.1-src/src/llvm-project/lldb/docs/use/ |
| H A D | qemu-testing.rst | 1 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
|
| /dports/devel/tinygo/tinygo-0.14.1/llvm-project/lldb/docs/resources/ |
| H A D | build.rst | 13 LLDB sources.
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
119 Building LLDB with CMake
163 * the main build-tree for LLDB in ``/path/to/lldb-build``
304 * ``LLDB_BUILD_FRAMEWORK:BOOL``: Builds the LLDB.framework.
329 Build, test and install a distribution of LLDB from the `monorepo
346 Build LLDB standalone for development with Xcode:
400 Cross-compiling LLDB
407 LLDB on your host.
[all …]
|
| /dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/lldb/docs/resources/ |
| H A D | build.rst | 13 LLDB sources.
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
128 Building LLDB with CMake
172 * the main build-tree for LLDB in ``/path/to/lldb-build``
305 * ``LLDB_BUILD_FRAMEWORK:BOOL``: Builds the LLDB.framework.
330 Build, test and install a distribution of LLDB from the `monorepo
347 Build LLDB standalone for development with Xcode:
401 Cross-compiling LLDB
408 LLDB on your host.
[all …]
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/lldb/test/API/commands/expression/import-std-module/empty-module/root/usr/include/c++/v1/ |
| H A D | algorithm | 1 // 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
|
| /dports/devel/tinygo/tinygo-0.14.1/llvm-project/lldb/packages/Python/lldbsuite/test/commands/expression/import-std-module/empty-module/root/usr/include/c++/v1/ |
| H A D | algorithm | 1 // 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
|
| /dports/devel/wasi-libcxx/llvm-project-13.0.1.src/lldb/test/API/commands/expression/import-std-module/empty-module/root/usr/include/c++/v1/ |
| H A D | algorithm | 1 // 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
|
| /dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/lldb/test/API/commands/expression/import-std-module/empty-module/root/usr/include/c++/v1/ |
| H A D | algorithm | 1 // 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
|
| /dports/devel/llvm12/llvm-project-12.0.1.src/lldb/test/API/commands/expression/import-std-module/empty-module/root/usr/include/c++/v1/ |
| H A D | algorithm | 1 // 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
|
| /dports/lang/rust/rustc-1.58.1-src/src/llvm-project/lldb/test/API/commands/expression/import-std-module/empty-module/root/usr/include/c++/v1/ |
| H A D | algorithm | 1 // 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
|