Searched refs:GDB (Results 1 – 25 of 89) sorted by relevance
1234
2 Debugging JIT-ed Code With GDB9 GDB (as well as most debuggers) can be quite painful. Debuggers generally13 In order to communicate the necessary debug info to GDB, an interface for15 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. When20 GDB attaches to a process, it puts a breakpoint in this function and loads all22 function, GDB catches the breakpoint signal, loads the new object file from23 the inferior's memory, and resumes the execution. In this way, GDB can get the26 GDB Version29 In order to debug code JIT-ed by LLVM, you need GDB 7.0 or newer, which is[all …]
29 When running a QEMU binary, you may chose to run it interactively with GDB, or32 Running Without GDB34 When running without GDB, the firmware will execute normally without requiring43 Run With GDB45 When running with GDB, execution of the binary will begin in a halted state. To46 begin running the code, you must connect using GDB, set any breakpoints you51 # Start the VM and GDB server.
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 %s10 …ple=x86_64-pc-linux -filetype=obj < %s | llvm-readobj -sections - | FileCheck --check-prefix=GDB %s13 … -filetype=obj -debugger-tune=gdb < %s | llvm-readobj -sections - | FileCheck --check-prefix=GDB %s18 ; GDB-NOT: apple_names19 ; GDB: debug_pubnames20 ; GDB-NOT: apple_names
58 [ "$GDB" = "" ]; then59 GDB=gdb112 …$GDB --batch -q --ex "r $use_args <$crash" --ex 'back' --ex 'disass $pc, $pc+16' --ex 'info reg' -…114 …$GDB --batch -q --ex "r $use_args" --ex 'back' --ex 'disass $pc, $pc+16' --ex 'info reg' --ex 'qui…
7 An ergonomic and easy-to-integrate implementation of the [GDB Remote Serial Protocol](https://sourc…9 …/base/singlethread/trait.SingleThreadBase.html) trait, you can have a rich GDB debugging session u…11 …extensions) (IDETs) to expose fine-grained, zero-cost control over enabled GDB protocol features _…23 …d of simply exposing the underlying GDB protocol "warts and all", `gdbstub` tries to abstract as m…24 …- Instead of having to dig through [obscure XML files deep the GDB codebase](https://github.com/…25 …- Organizes GDB's countless optional protocol extensions into a coherent, understandable, and ty…36 …test/gdbstub/conn/trait.Connection.html) interface to communicate with the GDB server. As long as …46 …ust's type system in enforcing GDB protocol invariants at compile time, it's often been the case t…54 The GDB Remote Serial Protocol is surprisingly complex, supporting advanced features such as remote…56 - Base GDB Protocol[all …]
6 # The GDB client may core dump if the target is implemented incorrectly
6 description: "An implementation of the GDB Remote Serial Protocol in Rust"
3 description = "An implementation of the GDB Remote Serial Protocol in Rust"
117 GDB=$optarg283 --script=<file> Specify extra GDB init script.602 if [ -z "$GDB" ]; then603 GDB=$(get_ndk_host_gdb_client "$ANDROID_NDK_ROOT")604 if [ -z "$GDB" ]; then608 log "Host gdb client: $GDB"923 exec $GDB "\$@"935 log "Launching gdb client: $GDB $GDB_ARGS -x $COMMANDS"938 $CGDB -d $GDB -- $GDB_ARGS -x "$COMMANDS"940 $GDB $GDB_ARGS -x "$COMMANDS"
86 ## GDB Support88 crosvm supports [GDB Remote Serial Protocol] to allow developers to debug guest kernel via GDB98 Then, you can start GDB in another shell.108 For general techniques for debugging the Linux kernel via GDB, see this [kernel documentation].
5 e.g: This PR implements the `foobar` extension, based off the GDB documentation [here](https://sour…23 …- [ ] Included output of running `examples/armv4t` with `RUST_LOG=trace` + any relevant GDB output…39 <summary>GDB output</summary>62 Waiting for a GDB connection on "127.0.0.1:9001"...89 GDB queried if it was attached to a process with PID 1105 PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"
30 adapted to other IDEs' GDB integration.32 VS Code comes with lldb support, but this workflow needs a GDB extension. Search for 'Native Debug'41 "name": "Android GDB",
120 #. Connect GDB to the running OpenOCD instance in terminal B142 GDB and the device. To run it for the Discovery board:169 Step 2: Start GDB and connect to the OpenOCD server171 Start GDB pointing to the correct .elf file, and tell it to connect to the190 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.
26 ## Debugging fuzzers with GDB36 # Run the Docker image containing GDB.
17 from GStreamer using GDB.39 GStreamer using GDB.
70 GDB section [33] '.gdb_index' at offset 0xe76 contains 8383 bytes :101 GDB section [33] '.gdb_index' at offset 0xe76 contains 8399 bytes :
3 DriverName=GDB
10 -g, --gdb Launch GDB
11 -g, --gdb Launch GDB
46 # GDB
9 ### Debug with GDB
158 The GDB protocol only requires that targets implement support for _continuing_ execution - support …160 > Note: this isn't actually true in practice, thanks to a bug in the mainline GDB client... See the…168 …et to hit some kind of stop condition. In this model, checking for pending GDB interrupts was quit…170 …ferring the responsibility of "selecting" between incoming stop events and GDB interrupts to highe…172 …ore of a "bookkeeping" purpose, recording what kind of resumption mode the GDB client has requeste…178 …in the target's `resume` method to perform "bookkeeping" regarding how the GDB client requested th…324 Single register access is not a required part of the GDB protocol, and as such, has been moved out …
93 GDB, // Tune debug info for gdb. enumerator