Searched refs:GDB (Results 1 – 25 of 46) sorted by relevance
12
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 …]
1330 Using GDB with dynamically loaded passes1333 Unfortunately, using GDB with dynamically loaded passes is not as easy as it1337 with GDB.1353 GDB is free software, covered by the GNU General Public License, and you are1356 There is absolutely no warranty for GDB. Type "show warranty" for details.1357 This GDB was configured as "sparc-sun-solaris2.6"...1384 Once you have the basics down, there are a couple of problems that GDB has,1387 * Inline functions have bogus stack information. In general, GDB does a pretty
3 ; We use existence of the debug_pubnames section to distinguish the GDB case,10 …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
28 export GDB=""55 echo "$@" "suppressed as $GDB version" $GDBVERSIONLINE "is <" $NEEDED 62 GDB=$163 ln -f -s "$GDB" gdbserver_tests/gdb
3 # GDB optimises "handle SIGNAL nostop noprint pass"
11 make regtest GDB=/path/to/another/gdb24 GDB command.
19 - For remote debugging support, working GDB is required (see below).94 Solaris port of GDB has a major flaw which prevents remote debugging from96 it is not present in the current GDB 7.6.2. This boils down to several98 - Use GDB shipped with Solaris 11.2 which has this flaw fixed.99 - Wait until GDB 7.7 becomes available (there won't be other 7.6.x releases).100 - Build GDB 7.6.2 with the fix by yourself using the following steps:
79 Debugging Valgrind with GDB104 (3) Do "handle SIGSEGV SIGILL nostop noprint" in GDB to prevent GDB from111 a breakpoint VG_(do_exec), you could do like this in GDB:131 GDB to the tool executable, which should be in the abovementioned178 Debugging the whole thing might imply to use up to 3 GDB:179 * a GDB attached to the Outer valgrind, allowing181 * a GDB using Outer gdbserver, allowing to183 * a GDB using Inner gdbserver, allowing to
75 $(top_srcdir)/gdbserver_tests/make_local_links $(GDB)
49 - Some gdb tests will fail when gdb (GDB) older than 7.5 is used and gdb is
64 Philippe Waroquiers wrote and maintains the embedded GDB server. He
196 * New and modified GDB server monitor features:198 - When a signal is reported in GDB, you can now use the GDB convenience203 with SIGNAL instead of the signal reported to GDB. Use 'signal 0' to206 - With GDB >= 7.10, the command 'target remote'209 file yourself, GDB will discover it itself. See GDB documentation about558 valgrind feature release. The built-in GDB server capabilities are607 - A new GDB server monitor command "info locks" giving the list of642 * New and modified GDB server monitor features:646 - The GDB server monitor command "v.info location <address>"653 ask the GDB server to stop at the start of program execution, at[all …]
16 * Integration with the built in GDB server:
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
88 GDB, // Tune debug info for gdb. enumerator
21 …race using any debugger. For example, if you're using GCC, you can use the GDB debugger as follows:23 $ gdb ./my_program # Start GDB on your program
191 We support 2 modes of debugging on Android using GDB wrapper scripts. These193 GDB client shell on your host. All necessary symbol files should
18 A technique used in GDB (and in uprobes, I believe), whereby the186 GDB supports python pretty printers. We migh want to hook this in
310 return llvm::DebuggerKind::GDB; in getDefaultDebuggerTuning()
264 clEnumValN(DebuggerKind::GDB, "gdb", "gdb"),
537 bool tuneForGDB() const { return DebuggerTuning == DebuggerKind::GDB; } in tuneForGDB()
144 === GDB server =========================================================
295 // debugging aid. GDB invokes this automagically
82 GDB however sophisticated C++ expressions are likely to fail.