| /dports/devel/llvm11/llvm-11.0.1.src/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/devel/wasi-compiler-rt13/llvm-project-13.0.1.src/llvm/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/devel/llvm90/llvm-9.0.1.src/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/devel/wasi-compiler-rt12/llvm-project-12.0.1.src/llvm/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/llvm/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/devel/wasi-libcxx/llvm-project-13.0.1.src/llvm/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/devel/llvm80/llvm-8.0.1.src/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/devel/tinygo/tinygo-0.14.1/llvm-project/llvm/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/devel/llvm70/llvm-7.0.1.src/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/devel/llvm13/llvm-project-13.0.1.src/llvm/test/DebugInfo/X86/ |
| H A D | debugger-tune.ll | 8 …apple-darwin12 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
14 …type=obj -debugger-tune=lldb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=LLDB %s
20 ; LLDB: DW_AT_APPLE_optimized
21 ; LLDB: DW_OP_form_tls_address
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/devel/tinygo/tinygo-0.14.1/llvm-project/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/devel/wasi-libcxx/llvm-project-13.0.1.src/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/devel/llvm12/llvm-project-12.0.1.src/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/lang/rust/rustc-1.58.1-src/src/llvm-project/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/devel/llvm-devel/llvm-project-f05c95f10fc1d8171071735af8ad3a9e87633120/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/devel/wasi-compiler-rt13/llvm-project-13.0.1.src/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/devel/wasi-compiler-rt12/llvm-project-12.0.1.src/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/devel/qtcreator/qt-creator-opensource-src-5.0.3/doc/qtcreator/src/debugger/creator-only/ |
| H A D | creator-debugger-setup.qdoc | 80 Console Debugger CDB is needed. On \macos and Linux, the LLDB debugger
93 \li GDB, LLDB
101 \li LLDB, FSF GDB (experimental)
127 \section2 Supported LLDB Versions
129 The LLDB native debugger has similar functionality to the GDB debugger. LLDB
131 LLDB is typically used with the Clang compiler (even though you can use it
134 On \macos you can use the LLDB version delivered with Xcode or build from source.
135 The minimum supported version is LLDB 320.4.
137 On Linux, the minimum supported version is LLDB 3.8.
229 \section2 LLDB
[all …]
|
| /dports/devel/llvm13/llvm-project-13.0.1.src/lldb/docs/use/ |
| H A D | remote.rst | 9 To enable remote debugging, LLDB employs a client-server architecture. The
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
15 LLDB also consists of a platform binary, which is responsible for performing
19 In order to reduce code complexity and improve remote debugging experience LLDB
45 statically linked with the rest of LLDB (unlike lldb, which dynamically links
54 of the binaries. More information on cross-compiling LLDB can be found on the
74 On the local system, you need to let LLDB know that you intend to do remote
152 This will cause LLDB to create a target with the "a.out" executable that you
153 cross built. The "run" command will cause LLDB to upload "a.out" to the
[all …]
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/lldb/docs/status/ |
| H A D | releases.rst | 7 Nightly builds of LLDB are packaged and tested from trunk:
14 LLDB is packaged in most of the Debian & Ubuntu releases and in pkgsrc (NetBSD).
|
| /dports/devel/wasi-libcxx/llvm-project-13.0.1.src/lldb/docs/status/ |
| H A D | releases.rst | 7 Nightly builds of LLDB are packaged and tested from trunk:
14 LLDB is packaged in most of the Debian & Ubuntu releases and in pkgsrc (NetBSD).
|
| /dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/lldb/docs/status/ |
| H A D | releases.rst | 7 Nightly builds of LLDB are packaged and tested from trunk:
14 LLDB is packaged in most of the Debian & Ubuntu releases and in pkgsrc (NetBSD).
|
| /dports/devel/llvm12/llvm-project-12.0.1.src/lldb/docs/status/ |
| H A D | releases.rst | 7 Nightly builds of LLDB are packaged and tested from trunk:
14 LLDB is packaged in most of the Debian & Ubuntu releases and in pkgsrc (NetBSD).
|