jankratochvil added a comment. In https://reviews.llvm.org/D53255#1267850, @labath wrote:
> It looks like it should be easy to write a test for this by hand-crafting a > minimal .s file and feeding it to lldb-test. Even with such a crafted file (in lldb-repro.tar.xz <https://people.redhat.com/jkratoch/lldb-repro.tar.xz>) I haven't found a way how to call `DWARFUnit::ExtractUnitDIEIfNeeded()` first. LLDB will always call `DWARFUnit::ExtractDIEsRWLocked()` first which cannot reproduce the bug. @xbolva00's file must have something special that `process launch -s` does call `DWARFUnit::ExtractUnitDIEIfNeeded()` first, my testcase does not. As I guess @xbolva00 cannot provide that file to us I think it would be enough to see a backtrace to the first call of `DWARFUnit::ExtractUnitDIEIfNeeded()` to find it out. Repository: rL LLVM https://reviews.llvm.org/D53255 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
