public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29412] libabigail 2.1.1 Assertion metabug
Date: Tue, 11 Oct 2022 21:56:32 +0000	[thread overview]
Message-ID: <bug-29412-9487-0qo8Z1KPjz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29412-9487@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29412

Ben Woodard <woodard at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|libabigail 2.1 Assertion    |libabigail 2.1.1 Assertion
                   |metabug                     |metabug

--- Comment #4 from Ben Woodard <woodard at redhat dot com> ---
libabigail 2.1 has been released. I'm currently testing all of F37 against the
latest trunk as of 4c5f44473e9f7c0a561174fdc6cc89f40dd9892a and will verify
that 
29324 29331 29333 29339 29340 29345 29346 do not still exist.

Currently the following packages from F37 crash with an assert:

matreshka
abipkgdiff: ../../../libabigail/src/abg-ir.cc:8712: abigail::interned_string
abigail::ir::get_generic_anonymous_internal_type_name(const decl_base*):
Assertion `__abg_cond__' failed.

--- gcc
abipkgdiff: ../../../libabigail/src/abg-ir-priv.h:687: void
abigail::ir::environment::priv::pop_composite_type_comparison_operands(const
abigail::ir::type_base*, const abigail::ir::type_base*): Assertion
`__abg_cond__' failed.

and the ones related to ocaml-*, planets, and why3

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-10-11 21:56 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 15:38 [Bug default/29412] New: " woodard at redhat dot com
2022-07-26 15:42 ` [Bug default/29412] " woodard at redhat dot com
2022-07-26 18:49 ` woodard at redhat dot com
2022-07-26 20:17 ` woodard at redhat dot com
2022-07-27  0:12 ` [Bug default/29412] libabigail 2.1 " woodard at redhat dot com
2022-07-28 18:34 ` woodard at redhat dot com
2022-07-28 18:43 ` woodard at redhat dot com
2022-10-11 21:56 ` woodard at redhat dot com [this message]
2022-10-11 22:14 ` [Bug default/29412] libabigail 2.1.1 " woodard at redhat dot com
2022-10-14 16:02 ` woodard at redhat dot com
2022-10-14 18:53 ` woodard at redhat dot com
2022-10-14 19:04 ` woodard at redhat dot com
2022-10-14 19:13 ` woodard at redhat dot com
2022-10-14 19:48 ` woodard at redhat dot com
2022-10-14 21:10 ` woodard at redhat dot com
2022-10-14 21:30 ` woodard at redhat dot com
2022-10-14 22:15 ` woodard at redhat dot com
2022-12-16 20:27 ` [Bug default/29412] libabigail 2.2 " woodard at redhat dot com
2023-01-07  0:39 ` woodard at redhat dot com
2023-01-09 19:28 ` woodard at redhat dot com
2023-01-09 20:13 ` woodard at redhat dot com
2023-03-10 18:53 ` dodji at redhat dot com
2023-03-13 16:54 ` dodji at redhat dot com
2023-03-14 10:25 ` dodji at redhat dot com
2023-03-23 17:20 ` dodji at redhat dot com
2023-03-23 22:54 ` woodard at redhat dot com
2023-03-23 23:13 ` woodard at redhat dot com
2023-03-24 17:35 ` dodji at redhat dot com
2023-03-26 15:01 ` dodji at redhat dot com
2023-03-26 23:17 ` dodji at redhat dot com
2023-03-31 17:02 ` woodard at redhat dot com
2023-03-31 18:47 ` woodard at redhat dot com
2023-03-31 21:30 ` dodji at redhat dot com
2023-04-03 22:09 ` woodard at redhat dot com
2023-04-07 18:16 ` dodji at redhat dot com
2023-04-07 18:23 ` dodji at redhat dot com
2023-04-11 14:45 ` dodji at redhat dot com
2023-04-11 14:47 ` dodji at redhat dot com
2023-04-11 14:49 ` dodji at redhat dot com
2023-04-11 14:51 ` dodji at redhat dot com
2023-04-11 15:40 ` dodji at redhat dot com
2023-04-11 15:41 ` dodji at redhat dot com
2023-04-11 15:41 ` dodji at redhat dot com
2023-05-18 21:23 ` [Bug default/29412] libabigail 2.3 " woodard at redhat dot com
2023-05-18 22:03 ` [Bug default/29412] libabigail 2.3 Assertion / crash metabug woodard at redhat dot com
2024-04-04 15:14 ` 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-29412-9487-0qo8Z1KPjz@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).