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

Yuri yuri at rawbw.com
Thu Feb 20 14:16:36 PST 2014

On 02/20/2014 14:07, David Blaikie wrote:
> Certainly there are bugs, but practically speaking I wouldn't characterize
> clang-generated debug info to be "barely passable". It generally works for
> me - it passes much of the GDB 7.5 test suite successfully.

Clang works, but I am getting an impression that any deviations from 
what clang does causes troubles.
I don't know, every time I look, I find something wrong with resulting 

> (this is all predicated on: "at -O0" - optimized debug info is another
> story entirely. Though there are even issues with locations (and sometimes
> even types!) at -O0, but they're pretty rare in my experience - I use Clang
> to debug Clang day-to-day and only every few months do I hit a bug)

Yes, my test case is for -O0 and CL=Large. Debug info for optimized code 
is a different issue, you are right.


More information about the llvm-dev mailing list