Hello, 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? -Philippe
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
