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: http://llvm.org/bugs/show_bug.cgi?id=18866

Yuri

_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev

Reply via email to