Lines Matching refs:GDB

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
30 available on most modern distributions of Linux.  The version of GDB that
39 GDB.  This is due to MCJIT's ability to use the MC emitter to provide full
40 DWARF debugging information to GDB.
84 code via ``lli`` inside GDB: