From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24441] Some crashes found by fuzzing
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24441-11298-R8pRG2oh6z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24441-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24441
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Looking at the assertions reproducible with trunk, prefixed with occurrence
count:
1257 dwz: dwz.c:1768: read_loclist: Assertion `ptr + len <= endsec' failed.
PR24172
60 dwz: dwz.c:8782: write_die: Assertion `refd != NULL' failed.
PR24169
56 dwz: dwz.c:8552: adjust_exprloc: Assertion `refd != NULL &&
!refd->die_remove' failed.
PR24195
48 dwz: dwz.c:9901: read_dwarf: Assertion `data != NULL' failed.
New
46 dwz: dwz.c:7859: update_new_die_offsets: Assertion
`die->u.p2.die_intracu_udata_size == 0 || die->die_ref_seen' failed.
New
14 dwz: dwz.c:7533: build_abbrevs_for_die: Assertion `refd != NULL'
failed.
New
2 dwz: dwz.c:8575: adjust_exprloc: Assertion `refd != NULL' failed.
New
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2019-04-15 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/24441] New: " ago at gentoo dot org
2019-01-01 0:00 ` vries at gcc dot gnu.org [this message]
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-24441-11298-R8pRG2oh6z@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).