From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19138] Assertion failure ../../src/abg-dwarf-reader.cc:3629
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-19138-9487-AHgMtI7ZLE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19138-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19138
--- Comment #3 from Ben Woodard <woodard at redhat dot com> ---
This is still occurring with quite some frequency with the latest git repo up
through:
6f00afe Fix regression on the support for alternate debug info files
The test has just started and has only been running for about 1/2 an hour and I
already have 189 recorded incidents of this assertion failing. Therefore I
would argue that this bug should be fixed before the final release.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-01-06 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 [Bug default/19138] New: " woodard at redhat dot com
2015-01-01 0:00 ` [Bug default/19138] " woodard at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2016-01-01 0:00 ` woodard at redhat dot com [this message]
2016-01-01 0:00 ` [Bug default/19138] Failure to relate variables address from DWARF and ELF dodji at redhat dot com
2016-01-01 0:00 ` [Bug default/19138] Assertion failure ../../src/abg-dwarf-reader.cc:3629 woodard at redhat dot com
2016-01-01 0:00 ` woodard at redhat dot com
2016-01-01 0:00 ` [Bug default/19138] Failure to relate variables address from DWARF and ELF dodji at redhat dot com
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-19138-9487-AHgMtI7ZLE@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@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).