From: "romain.geissler at amadeus dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29650] New: "Assertion `__abg_cond__' failed." with with libabigail 2.1
Date: Mon, 03 Oct 2022 19:14:46 +0000 [thread overview]
Message-ID: <bug-29650-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29650
Bug ID: 29650
Summary: "Assertion `__abg_cond__' failed." with with
libabigail 2.1
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: romain.geissler at amadeus dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
Hi,
I am having issues with libabigail 2.1 we didn't have with the previous
version. We get in quite some places errors like:
abidiff: /workdir/src/libabigail-2.1/src/abg-default-reporter.cc:375: virtual
void abigail::comparison::default_reporter::report(const
abigail::comparison::qualified_type_diff&, std::ostream&, const string&) const:
Assertion `__abg_cond__' failed.
I will try to attach (if it's not too big) an reproducer with the xalan open
source library 1.11 vs 1.12, but we also have similar failures with proprietary
software I can't really upload here. Just untar the tarball into a directory
and run:
abidiff --no-unreferenced-symbols libxalan-c.so.111.0 libxalan-c.so.112.0
Cheers,
Romain
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-03 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 19:14 romain.geissler at amadeus dot com [this message]
2022-10-03 19:22 ` [Bug default/29650] " romain.geissler at amadeus dot com
2022-10-03 19:23 ` romain.geissler at amadeus dot com
2022-10-03 19:24 ` romain.geissler at amadeus dot com
2022-10-03 19:25 ` romain.geissler at amadeus dot com
2022-10-07 20:30 ` dodji at redhat dot com
2022-10-10 15:19 ` dodji at redhat dot com
2022-10-10 15:20 ` dodji at redhat dot com
2022-10-10 15:24 ` romain.geissler at amadeus dot com
2022-10-10 16:22 ` dodji at redhat dot com
2022-10-10 18:36 ` romain.geissler at amadeus dot com
2022-10-11 9:49 ` Dodji Seketeli
2022-10-10 21:23 ` woodard at redhat dot com
2022-10-11 9:49 ` dodji at seketeli dot 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-29650-9487@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).