arvindm95 / unladen-swallow

Automatically exported from code.google.com/p/unladen-swallow
Other
0 stars 0 forks source link

Need support for debugging LLVM-generated machine code #35

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
We currently don't have a good way of debugging the machine code that comes
out of LLVM's JIT compiler.

To the best of my knowledge, LLVM doesn't emit debug information for JITted
code. Even if it did, there's no way to tell gdb to read this information.
However, there is support in the LLVM and gdb communities for fixing both
of these issues.

References:
- http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-March/021255.html
- http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-April/021421.html
- http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-April/021424.html
- http://wiki.llvm.org/HowTo:_Tell_GDB_about_JITted_code

Original issue reported on code.google.com by collinw on 27 May 2009 at 9:42

GoogleCodeExporter commented 8 years ago

Original comment by collinw on 27 May 2009 at 10:12

GoogleCodeExporter commented 8 years ago
Reid, is there anything else that needs to be done for this? As far as I can 
tell, we're in 
good shape with your changes included in gdb 7.0.

Original comment by collinw on 11 Jan 2010 at 7:55

GoogleCodeExporter commented 8 years ago
It would be sweet if we could get these changes into the gdb that Apple ships 
so that
with their next Xcode devtools release OS X CPython developers will be able to
benefit from this.  I think a sizeable number of CPython devs use MacBooks.

I think that would involve talking to DannyB and the Apple debugger folks so 
that we
can do all that copyright assignment gobledigook.  They may not want to deal 
with
merging the patch in, but LLVM is their baby so they should be interested.

There's also this bug (it doesn't affect us) which I should keep track of and 
fix:
http://sourceware.org/bugzilla/show_bug.cgi?id=11094

Original comment by reid.kle...@gmail.com on 11 Jan 2010 at 10:46

GoogleCodeExporter commented 8 years ago
We've gotten permission from Google's engi-lawyer to relicense the changes if 
need be. 
I've reached out to Apple's debugger people about getting the patches 
integrated into 
their development tree.

Original comment by collinw on 15 Jan 2010 at 10:10