[lldb-dev] LTO debug info

Philippe Lavoie via lldb-dev lldb-dev at lists.llvm.org
Mon Apr 25 13:37:00 PDT 2016


We noticed an issue with dwarf parsing when debugging a large application compiled with LTO.

Since an LTO application's debug info can have inter-compile-unit references, (for example: a type defined in one compile-unit and used in another) we noticed that the "m_type_index" vector in SymbolFileDWARF can get corrupted. This is because many index structures in SymbolFileDWARF are generated in parallel.

Is is a bug or is it expected to be the compiler's/linker's job to generate self-contained DWARF data without inter-CU references?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20160425/14893933/attachment.html>

More information about the lldb-dev mailing list