kimanh added a comment.
> If you do not want to debug those libraries cannot you just strip debug info > from them (`llvm-strip -g`)? Oh, stripping debug info may work. We're on the Chrome DevTools team and we're working on a DWARF-based debugging extension for C/C++. Ideally we'd like to have as few steps as possible that are required for our users to take, in order to successfully debug their application on the web. We'll keep this in mind. > Wouldn't be best to generate `.debug_names` for those 3rd party libraries? > GDB has `gdb-add-index` but its `.gdb_index` has not enough information to be > useful for LLDB. Still LLDB could generate `.debug_names` out of its internal > representation in `ManualDWARFIndex`. That would be useful also for debugging > binaries from non-clang compilers. Ah, to make sure that I understand it correctly: using `gdb-add-index` would help `ManualDWARFIndex` to generate a `.debug_names`? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D106355/new/ https://reviews.llvm.org/D106355 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
