Searched refs:GDB (Results 1 – 25 of 109) sorted by relevance
12345
| /external/llvm-project/llvm/docs/ |
| D | DebuggingJITedCode.rst | 2 Debugging JIT-ed Code With GDB
9 GDB (as well as most debuggers) can be quite painful. Debuggers generally
13 In order to communicate the necessary debug info to GDB, an interface for
15 GDB and LLVM MCJIT. At a high level, whenever MCJIT generates new machine code,
19 (``__jit_debug_register_code``) marked noinline that GDB knows about. When
20 GDB attaches to a process, it puts a breakpoint in this function and loads all
22 function, GDB catches the breakpoint signal, loads the new object file from
23 the inferior's memory, and resumes the execution. In this way, GDB can get the
26 GDB Version
29 In order to debug code JIT-ed by LLVM, you need GDB 7.0 or newer, which is
[all …]
|
| /external/llvm/docs/ |
| D | DebuggingJITedCode.rst | 2 Debugging JIT-ed Code With GDB
9 GDB (as well as most debuggers) can be quite painful. Debuggers generally
13 In order to communicate the necessary debug info to GDB, an interface for
15 GDB and LLVM MCJIT. At a high level, whenever MCJIT generates new machine code,
19 (``__jit_debug_register_code``) marked noinline that GDB knows about. When
20 GDB attaches to a process, it puts a breakpoint in this function and loads all
22 function, GDB catches the breakpoint signal, loads the new object file from
23 the inferior's memory, and resumes the execution. In this way, GDB can get the
26 GDB Version
29 In order to debug code JIT-ed by LLVM, you need GDB 7.0 or newer, which is
[all …]
|
| /external/pigweed/targets/lm3s6965evb-qemu/ |
| D | target_docs.rst | 29 When running a QEMU binary, you may chose to run it interactively with GDB, or
32 Running Without GDB
34 When running without GDB, the firmware will execute normally without requiring
43 Run With GDB
45 When running with GDB, execution of the binary will begin in a halted state. To
46 begin running the code, you must connect using GDB, set any breakpoints you
51 # Start the VM and GDB server.
|
| /external/llvm/test/DebugInfo/X86/ |
| D | debugger-tune.ll | 3 ; We use existence of the debug_pubnames section to distinguish the GDB case,
9 …e=x86_64-pc-freebsd -filetype=obj < %s | llvm-readobj -sections - | FileCheck --check-prefix=GDB %s
10 …ple=x86_64-pc-linux -filetype=obj < %s | llvm-readobj -sections - | FileCheck --check-prefix=GDB %s
13 … -filetype=obj -debugger-tune=gdb < %s | llvm-readobj -sections - | FileCheck --check-prefix=GDB %s
18 ; GDB-NOT: apple_names
19 ; GDB: debug_pubnames
20 ; GDB-NOT: apple_names
|
| /external/llvm-project/lldb/test/Shell/Reproducer/ |
| D | TestDump.test | 21 # RUN: %lldb -b -o 'reproducer dump -p gdb -f %t.repro' | FileCheck %s --check-prefix GDB
22 # GDB: send packet: $QStartNoAckMode#b0
23 # GDB: read packet: $OK#9a
28 # RUN: not %lldb -b -o 'reproducer dump -p gdb -f %t.repro' 2>&1 | FileCheck %s --check-prefix GDB-…
29 # GDB-ERROR: error: Unable to create GDB loader.
|
| /external/tensorflow/tensorflow/lite/micro/kernels/vexriscv/utils/ |
| D | README.md | 9 application is running on Renode with GDB session attached or with Renode's
21 In the following guide with GDB, we will be using the example gdb script
40 ### Start GDB server on Renode on port 8833
46 ### Launch GDB
48 First you need to find a proper GDB executable for your target architecture,
49 here, we will follow Antmicro's repo and use the riscv GDB executable from
52 Usage: `[GDB] -x [GDB_SCRIPT] [TFLM_BINARY]`
58 ### Connect GDB to Renode's gdbserver on the same port
65 # Run the function in the GDB script with required parameter
81 # obtained from GDB and only keep top 7 most frequent functions in the
[all …]
|
| /external/rust/crates/gdbstub/ |
| D | README.md | 6 An ergonomic and easy-to-integrate implementation of the [GDB Remote Serial Protocol](https://sourc…
11 …ke other GDB stub libraries, which simply expose the underlying GDB protocol "warts and all", `gdb…
12 …- For example, instead of having to dig through some [obscure XML files deep the GDB codebase](h…
18 …ub/latest/gdbstub/trait.Connection.html) interface to communicate with the GDB server. As long as …
34 … the PC after a breakpoint is hit), or were related to certain unimplemented GDB protocol features.
36 …ust's type system in enforcing GDB protocol invariants at compile time, it's often been the case t…
42 The GDB Remote Serial Protocol is surprisingly complex, supporting advanced features such as remote…
44 - Base GDB Protocol
50 …ugging features as well. At the moment, `gdbstub` implements the following GDB protocol extensions:
64 - Extend the GDB protocol with custom debug commands using GDB's `monitor` command
[all …]
|
| D | .gitignore | 6 # GDB will core dump if the target is implemented incorrectly (which it often is during debugging)
|
| D | METADATA | 2 description: "An implementation of the GDB Remote Serial Protocol in Rust"
|
| D | Cargo.toml.orig | 3 description = "An implementation of the GDB Remote Serial Protocol in Rust"
|
| /external/llvm-project/lld/test/ELF/ |
| D | debug-gnu-pubnames.s | 10 # RUN: llvm-readobj --sections %t2.exe | FileCheck %s --check-prefix=GDB
11 # GDB-NOT: .debug_gnu_pubnames
12 # GDB-NOT: .debug_gnu_pubtypes
|
| /external/tensorflow/tensorflow/lite/micro/examples/micro_speech/apollo3/ |
| D | README.md | 7 * To print out the neural net's inference scores, run GDB and source
9 * To save the captured audio to a text file (captured\_data.txt), run GDB
36 * Run with the preprocessor\_1k\_cmsis\_test.cmd GDB command file
54 * Run with the preprocessor\_1k\_micro\_test.cmd GDB command file
73 containing data dumped from GDB (specifically the verilog format) and
80 * **get\_yesno\_data.cmd**: A GDB command file that runs preprocessor_test
86 * **preprocessor_1k_cmsis_test.cmd**: GDB command file for the CMSIS
88 * **preprocessor_1k_micro_test.cmd**: GDB command file for the Micro-Lite
90 * **preprocessor_test.cmd**: GDB command file for the preprocessor test
91 * **pushbutton_cmsis_scores.cmd**: GDB command file that runs
[all …]
|
| /external/llvm-project/llvm/test/DebugInfo/X86/ |
| D | debugger-tune.ll | 9 …6_64-pc-freebsd -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=GDB %s
10 …x86_64-pc-linux -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=GDB %s
13 …letype=obj -debugger-tune=gdb < %s | llvm-dwarfdump -debug-info - | FileCheck --check-prefix=GDB %s
17 ; GDB-NOT: DW_AT_APPLE_optimized
18 ; GDB-NOT: DW_OP_form_tls_address
|
| /external/oss-fuzz/docs/advanced-topics/ |
| D | debugging.md | 26 ## Debugging fuzzers with GDB
36 # Run the Docker image containing GDB.
|
| /external/pigweed/targets/stm32f429i-disc1/ |
| D | target_docs.rst | 120 #. Connect GDB to the running OpenOCD instance in terminal B
142 GDB and the device. To run it for the Discovery board:
169 Step 2: Start GDB and connect to the OpenOCD server
171 Start GDB pointing to the correct .elf file, and tell it to connect to the
190 This GDB was configured as "--host=x86_64-apple-darwin10 --target=arm-none-eabi".
194 Find the GDB manual and other documentation resources online at:
206 Now that the GDB instance is connected to the device, you can flash, run, and debug.
|
| /external/elfutils/tests/ |
| D | run-readelf-gdb_index.sh | 70 GDB section [33] '.gdb_index' at offset 0xe76 contains 8383 bytes :
101 GDB section [33] '.gdb_index' at offset 0xe76 contains 8399 bytes :
|
| /external/llvm-project/lldb/source/Plugins/JITLoader/ |
| D | CMakeLists.txt | 1 add_subdirectory(GDB)
|
| /external/eigen/bench/btl/libs/mtl4/ |
| D | .kdbgrc.main | 3 DriverName=GDB
|
| /external/llvm-project/lldb/docs/ |
| D | lldb-gdb-remote.txt | 1 LLDB has added new GDB server packets to better support multi-threaded and
2 remote debugging. Why? Normally you need to start the correct GDB and the
3 correct GDB server when debugging. If you have mismatch, then things go wrong
4 very quickly. LLDB makes extensive use of the GDB remote protocol and we
7 front. We also ran into performance issues with the existing GDB remote
11 registers a thread might have. Again with GDB, both sides pre-agree on how the
16 added above and beyond the standard GDB remote protocol packets.
25 // High. Any GDB remote server that can implement this should if the
31 communication interfaces (like sockets). Below GDB or LLDB will send this
33 from GDB/LLDB, and all lines that start with "read packet: " are from the GDB
[all …]
|
| /external/llvm-project/lldb/source/Plugins/JITLoader/GDB/ |
| D | JITLoaderGDBProperties.td | 8 Desc<"Enable GDB's JIT compilation interface (default: enabled on all platforms except macOS)">;
|
| /external/mesa3d/src/intel/tools/ |
| D | intel_stub_gpu.in | 10 -g, --gdb Launch GDB
|
| D | intel_dump_gpu.in | 11 -g, --gdb Launch GDB
|
| /external/pigweed/ |
| D | .dockerignore | 35 # GDB
|
| D | .gitignore | 35 # GDB
|
| /external/crosvm/ |
| D | README.md | 165 ### GDB Support
167 crosvm supports [GDB Remote Serial Protocol] to allow developers to debug guest
168 kernel via GDB.
177 Then, you can start GDB in another shell.
187 For general techniques for debugging the Linux kernel via GDB, see this
190 [GDB Remote Serial Protocol]: https://sourceware.org/gdb/onlinedocs/gdb/Remote-Protocol.html
|
12345