From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29688] New: gcc-gnat firebird and llvm7.0 from fedora 37 all assert when attempting a self-compare with 2.1
Date: Fri, 14 Oct 2022 19:36:22 +0000 [thread overview]
Message-ID: <bug-29688-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29688
Bug ID: 29688
Summary: gcc-gnat firebird and llvm7.0 from fedora 37 all
assert when attempting a self-compare with 2.1
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
fedabipkgdiff --self-compare -a --from fc37 firebird
Comparing the ABI of binaries between firebird-4.0.0.2496-8.fc37.aarch64.rpm
and firebird-4.0.0.2496-8.fc37.aarch64.rpm:
abipkgdiff: ../../../libabigail/src/abg-ir.cc:14680:
abigail::ir::type_base_sptr abigail::ir::canonicalize(type_base_sptr):
Assertion `__abg_cond__' failed.
Comparing the ABI of binaries between
firebird-devel-4.0.0.2496-8.fc37.aarch64.rpm and
firebird-devel-4.0.0.2496-8.fc37.aarch64.rpm:
Comparing the ABI of binaries between
libfbclient2-devel-4.0.0.2496-8.fc37.aarch64.rpm and
libfbclient2-devel-4.0.0.2496-8.fc37.aarch64.rpm:
So not much useful information.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-14 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 19:36 woodard at redhat dot com [this message]
2023-03-24 11:23 ` [Bug default/29688] " 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-29688-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).