I had subsequently discovered your COPR, which does work with the DWZ symbols and allow
debugging, however your version is missing Swift support, and so doesn't support Swift
function name demangling and variable display etc.
+1 for moving to -fdebug-types-section anyway.
On Sat, 26 Sep 2020, at 1:23 AM, Jan Kratochvil wrote:
> On Fri, 25 Sep 2020 13:43:40 +0200, Neal Gompa wrote:
> > On Fri, Sep 25, 2020 at 7:26 AM Ryan <ryan(a)testtoast.com> wrote:
> > >
> > > > == Benefit to Fedora ==
> > > > * Better compatibility with existing debugging and tracing tools,
> > > > primarily [https://lldb.llvm.org/
> > >
> > > Thanks for your work on this Ben and Jan, Just as an interested user, use
> > > of the DWZ format significantly limits Swift development on Fedora, as it
> > > is impossible to debug with LLDB when using system libraries.
> Currently you can use my off-trunk patchset build:
> dnf copr enable jankratochvil/lldb;dnf install
> > But that's fixable since there's a patchset to make LLDB understand
> > dwz, which was not submitted upstream for unstated reasons.
> The reasons are stated in other mails, re-stating here:
> * the support of DWZ is complicated for effective DWARF consumers like LLDB
> * the same DWZ size reduction can be achieved just by removing dead DIEs
> and -fdebug-types-section skeletons - not needing any DWZ nor DWZ support
> in consumers at all
> * the LLDB DWZ support is now scatterd across the LLDB DWARF codebase for
> every DIE type so it will require continuous maintenance during LLDB
> development from RH; Google+Apple will probably never use DWZ themselves.
> * the LLDB DWZ support is currently implemented in LLDB DWARF/ but LLDB
> is going to replace its DWARF code to clang's DWARF code which will then
> require rewriting the LLDB DWZ code from scratch