search for: _tell_gdb_about_jitted_code

...against GDB: http://web.mit.edu/rnk/www/jit-patch.diff And finally, the patch to LLVM is attached and uploaded to Rietveld: http://codereview.appspot.com/91042/show I know this code is sketchy and preliminary, but it's useful for us, and I have plans to improve it: http://wiki.llvm.org/HowTo:_Tell_GDB_about_JITted_code Please review! Thanks, Reid -------------- next part -------------- A non-text attachment was scrubbed... Name: gdb-elf-patch.diff Type: text/x-diff Size: 16778 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090708/5ebda977/attachment.diff>

On Wed, Jul 8, 2009 at 11:41 AM, Reid Kleckner<rnk at mit.edu> wrote: > Right now, GDB has no way to be told about JITed code.  I'm working on > adding such an interface, and the LLVM JIT would be the first client. Have you considered how this might be made to work for embedded targets where remote debugging is required? deep

...k to figure out the in memory objfile data structures and modify those directly. This was just the path that yielded results most quickly. >> I know this code is sketchy and preliminary, but it's useful for us, >> and I have plans to improve it: >> http://wiki.llvm.org/HowTo:_Tell_GDB_about_JITted_code > > I'm not entirely sure about the lazy debug symbols part, but > as far as I can tell neither are you :) Yeah, that's seeming less and less likely to happen. > The rest of it seems reasonable to me. Great! On Wed, Jul 8, 2009 at 12:27 PM, Sandeep Patel<deeppatel1987 at...

...embly. We'll need to get work done for this (or do it ourselves) on both your end and gdb's end, since it doesn't yet have hooks to register debug info like the exception system does. I've started a page on the wiki to track the state of the art for this: http://wiki.llvm.org/HowTo:_Tell_GDB_about_JITted_code Thanks! > 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 step into functions >> I've compiled with LLVM's JIT compiler. The a...

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

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 *);