From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24170] New: dwz: dwz.c:1985: checksum_die: Assertion `((!op_multifile && !rd_multifile && !fi_multifile) || cu != die_cu (ref)) && (!op_multifile || cu->cu_chunk == die_cu (ref)->cu_chunk)' failed.
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24170-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24170
Bug ID: 24170
Summary: dwz: dwz.c:1985: checksum_die: Assertion
`((!op_multifile && !rd_multifile && !fi_multifile) ||
cu != die_cu (ref)) && (!op_multifile || cu->cu_chunk
== die_cu (ref)->cu_chunk)' failed.
Product: dwz
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
Created attachment 11588
--> https://sourceware.org/bugzilla/attachment.cgi?id=11588&action=edit
0.debug.gz
[ See also "brc#995136 - dwz assertion on -m for golang-produced binaries" at
https://bugzilla.redhat.com/show_bug.cgi?id=995136 ]
On master +
https://build.opensuse.org/package/view_file/openSUSE:Factory/dwz/dwz-0.12-ignore-nobits.patch,
we get this assert for 0.debug:
...
$ cp 0.debug 1
$ cp 0.debug 2
$ dwz -m 3 1 2
dwz: dwz.c:1985: checksum_die: Assertion `((!op_multifile && !rd_multifile &&
!fi_multifile) || cu != die_cu (ref)) && (!op_multifile || cu->cu_chunk ==
die_cu (ref)->cu_chunk)' failed.
Aborted (core dumped)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-02-05 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 vries at gcc dot gnu.org [this message]
2019-01-01 0:00 ` [Bug default/24170] " vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-24170-11298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).