Lines Matching +full:- +full:no +full:- +full:sphinx
2 Debugging JIT-ed Code
10 disk, but for JITed code there is no such file to look for.
13 interface <https://sourceware.org/gdb/onlinedocs/gdb/JIT-Interface.html>`_
19 in-memory object file that contains the debug information in DWARF format.
20 MCJIT then adds this in-memory object file to a global list of dynamically
27 information for pure in-memory object files.
33 In order to debug code JIT-ed by LLVM, you need GDB 7.0 or newer, which is
44 feature must be enabled explicitly using the ``plugin.jit-loader.gdb.enable``
48 Debugging MCJIT-ed code
51 The emerging MCJIT component of LLVM allows full debugging of JIT-ed code with
55 Note that lli has to be passed the ``--jit-kind=mcjit`` flag to JIT the code
59 -------
66 Sphinx has the ability to automatically number these lines by adding
67 :linenos: on the line immediately following the `.. code-block:: c`, but
69 lines. Is this a Sphinx bug, or is it a CSS problem?
71 .. code-block:: c
79 7 while (--n > 1)
88 16 return -1;
90 18 int result = compute_factorial(firstletter - '0');
99 .. code-block:: bash
101 > export BINPATH=/workspaces/llvm-project/build/bin
102 > $BINPATH/clang -g -S -emit-llvm --target=x86_64-unknown-unknown-elf showdebug.c
104 (lldb) target create "/workspaces/llvm-project/build/bin/lli"
105 Current executable set to '/workspaces/llvm-project/build/bin/lli' (x86_64).
106 (lldb) settings set plugin.jit-loader.gdb.enable on
108 Breakpoint 1: no locations (pending).
110 (lldb) run --jit-kind=mcjit showdebug.ll 5
117 -> 3 if (n <= 1)
120 6 while (--n > 1)
131 6 while (--n > 1)
134 -> 9 }
147 …, fini=<unavailable>, rtld_fini=<unavailable>, stack_end=0x00007fffffffe108) at libc-start.c:308:16
156 14 return -1;
158 -> 16 int result = compute_factorial(firstletter - '0');
168 16 int result = compute_factorial(firstletter - '0');
171 -> 19 return result;