With b7111689a2ccec2f57343f1051ec8f1df5e89e5c = commit 2020-02-19 getting $subject which should have been fixed by PR 25109 but it is not. It is reproducible at least with these 233 packages: http://people.redhat.com/jkratoch/dwz-assert.pkglist
(In reply to Jan Kratochvil from comment #0) > With b7111689a2ccec2f57343f1051ec8f1df5e89e5c = commit 2020-02-19 > getting $subject which should have been fixed by PR 25109 but it is not. > > It is reproducible at least with these 233 packages: > http://people.redhat.com/jkratoch/dwz-assert.pkglist Can you attach a reproducer?
(In reply to Jan Kratochvil from comment #0) > It is reproducible at least with these 233 packages: > http://people.redhat.com/jkratoch/dwz-assert.pkglist FWIW, I've tried to make a reproducer myself by building binutils, which is in this list, but no luck.
Created attachment 12782 [details] .tar.xz b7111689a2ccec2f57343f1051ec8f1df5e89e5c = 2020-02-19 ~/redhat/dwz-git/dwz -m dwz.debug --odr 1.debug 2.debug ~/redhat/dwz-git/dwz: 1.debug: DWARF compression not beneficial - old size 317760 new size 317760 dwz: dwz.c:11404: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed. Aborted (core dumped) Although I find more a blocker for DWZ after 3+ years it still does not support DWARF-5; and not just its part as produced by GCC but also the DWARF-5 features produced by LLVM: PR 24726
This only reproduces with --odr. Without things work fine.
Posted fix: https://sourceware.org/pipermail/dwz/2021q1/000890.html
(In reply to Jan Kratochvil from comment #0) > With b7111689a2ccec2f57343f1051ec8f1df5e89e5c = commit 2020-02-19 > getting $subject which should have been fixed by PR 25109 but it is not. > PR25109 is related to die_no_multifile propagation, and the problem occurs independent of odr. This problem is related to CK_BAD propagation, and occurs only with odr. The two root causes are different, they just happen to trigger the same assert.
Fixed in commit https://sourceware.org/git/?p=dwz.git;a=commit;h=3312feb1783283cb072d094fce9e1f6255d5da63
*** Bug 25439 has been marked as a duplicate of this bug. ***