public inbox for
 help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <>
Subject: [Bug default/26252] dwz.c:11404: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed. #2
Date: Wed, 19 Aug 2020 19:05:13 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
                 CC|                            |jan.kratochvil at redhat dot com

--- Comment #3 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
Created attachment 12782

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'
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

You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-08-19 19:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 15:40 [Bug default/26252] New: " jan.kratochvil at redhat dot com
2020-08-18  9:23 ` [Bug default/26252] " vries at gcc dot
2020-08-18  9:54 ` vries at gcc dot
2020-08-19 19:05 ` jan.kratochvil at redhat dot com [this message]
2020-09-13 14:12 ` [Bug default/26252] [odr] " mark at klomp dot org
2021-02-16  9:14 ` vries at gcc dot
2021-02-16  9:21 ` vries at gcc dot
2021-02-22  7:55 ` vries at gcc dot
2021-02-23 13:11 ` vries at gcc dot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).