Hi, I'm looking for a way to map bitcode to the source code (C/C++) from which it was generated. For example, the Java class file format has an optional LineNumberTable attribute that maps each bytecode instruction to a source code line number: http://java.sun.com/docs/books/jvms/second_edition/html/ClassFile.doc.html#22856 Is there something analogous in the LLVM environment? Thanks, Trevor
Hi Trevor,> I'm looking for a way to map bitcode to the source code (C/C++) from > which it was generated. For example, the Java class file format has an > optional LineNumberTable attribute that maps each bytecode instruction > to a source code line number: > > http://java.sun.com/docs/books/jvms/second_edition/html/ClassFile.doc.html#22856 > > Is there something analogous in the LLVM environment? Thanks,this can be done using debug info. Check out http://llvm.org/docs/SourceLevelDebugging.html Ciao, Duncan.
On Feb 8, 2010, at 8:51 PM, Duncan Sands wrote:> this can be done using debug info. Check out > http://llvm.org/docs/SourceLevelDebugging.htmlWow, that threw me for a loop. I'm using the 2.6 release, thinking I was up to date, but its debug output doesn't look anything like what's described in the above link. It appears to document the upcoming 2.7 version, which for some reason produces different debug syntax than 2.6. For example, the llvm.dbg.stoppoint intrinsic function no longer exists in 2.7, and 2.6 has no "metadata" descriptors. Is there any information about these changes and why they were necessary? Also, is there an API for accessing the debug info? I looked through the Programmer's Manual but didn't see anything. Thanks, Trevor