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/26941] abidiff assert in build_or_get_type_decl when comparing a library to itself
Date: Mon, 30 Nov 2020 22:47:20 +0000	[thread overview]
Message-ID: <bug-26941-9487-euVn6pd6xb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26941-9487@http.sourceware.org/bugzilla/>

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

Ben Woodard <woodard at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |---

--- Comment #2 from Ben Woodard <woodard at redhat dot com> ---
I'm still reproducing this problem in 105 different cases with the libabigail
trunk up through commit 2417efb2

I guess that we assumed that all of these would have the same proximate cause
when in fact they have different causes. 

attached is the full list of files and the RPMs that they come from which still
exhibit this problem.

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

  parent reply	other threads:[~2020-11-30 22:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25  0:03 [Bug default/26941] New: " woodard at redhat dot com
2020-11-25  8:41 ` [Bug default/26941] " dodji at redhat dot com
2020-11-30 22:47 ` woodard at redhat dot com [this message]
2020-11-30 22:49 ` woodard at redhat dot com
2020-11-30 23:34 ` woodard at redhat dot com
2020-11-30 23:35 ` woodard at redhat dot com
2020-12-01 14:56 ` woodard 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-26941-9487-euVn6pd6xb@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).