Home
last modified time | relevance | path

Searched refs:GDB (Results 1 – 25 of 134) sorted by relevance

123456

/external/llvm/docs/
DDebuggingJITedCode.rst2 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/test/DebugInfo/X86/
Ddebugger-tune.ll3 ; 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/valgrind/gdbserver_tests/
Dmake_local_links28 export GDB=""
55 echo "$@" "suppressed as $GDB version" $GDBVERSIONLINE "is <" $NEEDED
62 GDB=$1
63 ln -f -s "$GDB" gdbserver_tests/gdb
Dnlpasssigalrm.vgtest3 # GDB optimises "handle SIGNAL nostop noprint pass"
DREADME_DEVELOPERS11 make regtest GDB=/path/to/another/gdb
24 GDB command.
/external/elfutils/tests/
Drun-readelf-gdb_index.sh70 GDB section [33] '.gdb_index' at offset 0xe76 contains 8383 bytes :
101 GDB section [33] '.gdb_index' at offset 0xe76 contains 8399 bytes :
/external/valgrind/
DREADME.solaris19 - For remote debugging support, working GDB is required (see below).
100 Solaris port of GDB has a major flaw which prevents remote debugging from
102 it is not present in the current GDB 7.6.2. This boils down to several
104 - Use GDB shipped with Solaris 11.2 which has this flaw fixed.
105 - Wait until GDB 7.7 becomes available (there won't be other 7.6.x releases).
106 - Build GDB 7.6.2 with the fix by yourself using the following steps:
DREADME_DEVELOPERS79 Debugging Valgrind with GDB
104 (3) Do "handle SIGSEGV SIGILL nostop noprint" in GDB to prevent GDB from
111 a breakpoint VG_(do_exec), you could do like this in GDB:
131 GDB to the tool executable, which should be in the abovementioned
178 Debugging the whole thing might imply to use up to 3 GDB:
179 * a GDB attached to the Outer valgrind, allowing
181 * a GDB using Outer gdbserver, allowing to
183 * a GDB using Inner gdbserver, allowing to
DMakefile.am76 $(top_srcdir)/gdbserver_tests/make_local_links $(GDB)
DREADME.mips44 - Some gdb tests will fail when gdb (GDB) older than 7.5 is used and gdb is
DAUTHORS64 Philippe Waroquiers wrote and maintains the embedded GDB server. He
DNEWS335 * New and modified GDB server monitor features:
338 Note that you must have GDB >= 7.11 to use 'catch syscall' with
681 * New and modified GDB server monitor features:
683 - When a signal is reported in GDB, you can now use the GDB convenience
688 with SIGNAL instead of the signal reported to GDB. Use 'signal 0' to
691 - With GDB >= 7.10, the command 'target remote'
694 file yourself, GDB will discover it itself. See GDB documentation about
1042 valgrind feature release. The built-in GDB server capabilities are
1091 - A new GDB server monitor command "info locks" giving the list of
1126 * New and modified GDB server monitor features:
[all …]
/external/eigen/bench/btl/libs/mtl4/
D.kdbgrc.main3 DriverName=GDB
/external/llvm/include/llvm/Target/
DTargetOptions.h87 GDB, // Tune debug info for gdb. enumerator
/external/ltp/testcases/kdump/doc/
DTEST_PLAN.txt25 - GDB
/external/valgrind/solaris/
DMakefile.in197 GDB = @GDB@
/external/valgrind/exp-dhat/tests/
DMakefile.in191 GDB = @GDB@
/external/valgrind/lackey/tests/
DMakefile.in194 GDB = @GDB@
/external/libcxx/docs/
DUsingLibcxx.rst115 GDB Pretty printers for libc++
118 GDB does not support pretty-printing of libc++ symbols by default. Unfortunately
/external/valgrind/shared/
DMakefile.in191 GDB = @GDB@
/external/eigen/doc/
DUnalignedArrayAssert.dox21 …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
/external/toolchain-utils/dejagnu/boards/
Dgdb.exp.in56 # We will be using the standard GDB remote protocol.
/external/clang/include/clang/Driver/
DToolChain.h315 return llvm::DebuggerKind::GDB; in getDefaultDebuggerTuning()
/external/valgrind/include/
DMakefile.in240 GDB = @GDB@
/external/valgrind/memcheck/tests/common/
DMakefile.in224 GDB = @GDB@

123456