Displaying 3 results from an estimated 3 matches for "gdb_13".
Did you mean:
gdb1
2009 Mar 31
2
[LLVMdev] Connecting JITted code to gdb
...very time the user gets to the gdb
prompt. There may be other problems I haven't though of.
It would be better to have an interface through which a JITting
library could tell gdb about newly-generated code. This could resemble
the overlay interface
(http://sourceware.org/gdb/current/onlinedocs/gdb_13.html#SEC108) or
the interface through which dynamic loaders tell gdb about
newly-loaded code. There are a couple considerations that are specific
to JITting, of course:
1. A JIT compiler generates new code frequently, and having to do
lots of extra work, especially while the debugger isn't att...
2009 Mar 27
0
[LLVMdev] Connecting JITted code to gdb
Run with -debug-only=jit.
Break on line 1148 of JITEmitter.cpp. The debugging message will tell
you the address and size of the function that was jitted. You can then
tell gdb to disassemble the code.
On Mar 26, 2009, at 11:35 PM, Jeffrey Yasskin wrote:
> Hi all. I'm working on the recently-announced unladen-swallow project,
> and I'm having a bit of trouble getting gdb to
2009 Mar 27
4
[LLVMdev] Connecting JITted code to gdb
Hi all. I'm working on the recently-announced unladen-swallow project,
and I'm having a bit of trouble getting gdb to step into functions
I've compiled with LLVM's JIT compiler. The attached a_module.ll is
the module I produce from compiling
def foo(r):
for i in r:
pass
I'm JIT-compiling and running foo() with:
typedef PyObject *(*NativeFunction)(PyFrameObject *);