[lldb-dev] [LLVMdev] How is variable info retrieved in debugging for executables generated by llvm backend?

Yuri yuri at rawbw.com
Thu Feb 20 13:58:13 PST 2014

On 02/18/2014 00:44, æšć‹‡ć‹‡ wrote:
> I ported llvm backend and lldb recently. Both tools can basically work.
> lldb is able to debug programs in asm style and frame unwinding is OK.
> But "frame variable XX" does not work because lldb is not able to determine
> the address of
> XX from debug info.

I recently did some work with the debug info as generated by llvm, and 
there are a lot of bugs. LLVM writes wrong DWARF info. My impression is 
that DWARF writer is barely passable with clang-generated code, or maybe 
it malfunctions with clang as well. People don't hold debug info to the 
same high standard as the code itself.

Here is an example when variable info generated is plain wrong: 


More information about the lldb-dev mailing list