public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dodji at seketeli dot org" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26769] assert when comparing libstdc++ to itself
Date: Tue, 17 Nov 2020 17:39:28 +0000	[thread overview]
Message-ID: <bug-26769-9487-SFDKsQE4PM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26769-9487@http.sourceware.org/bugzilla/>

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

--- Comment #7 from dodji at seketeli dot org ---
woodard at redhat dot com via Libabigail <libabigail@sourceware.org> a
écrit:

> https://sourceware.org/bugzilla/show_bug.cgi?id=26769
>
> --- Comment #6 from Ben Woodard <woodard at redhat dot com> ---
> This latest patch 9ab30d86bd853b4561a9490898b65fc1fd5a203e seems to have
> greatly improved the situation. I'm down to 56 failures rather than
> over 300.

Thanks for testing this Ben!

Before I can move forward on this, I need to get in a new test harness
to regression-test this.  The thing is that this binary has its debug
info stripped out and compressed with dwz, as part of the normal process
that binaries packaged in RPM for Fedora go through.

So I am looking into coming with a new abikpkgdiff --self-check <rpm>
option that would compare each binary in a rpm against its abixml
representation.  I would then add the rpm of libstdc++ to the testsuite
and have a new harness that would run abipkgdiff --self-check on it.

Once I have this, I can proceed with contemplating merging this in.

> However the majority of the remaining problems still seem to hit this problem
> just in a different way. 51/56 of the remaining failures look like
> this:

I see.  I'll look into this right away when I am done with the above.
Hopefully, fixing this will bring the number of issues down
dramatically.

Thanks for looking into this.

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

  parent reply	other threads:[~2020-11-17 17:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22  5:10 [Bug default/26769] New: " woodard at redhat dot com
2020-10-22  6:00 ` [Bug default/26769] " woodard at redhat dot com
2020-10-23  4:48 ` woodard at redhat dot com
2020-10-23 22:22 ` woodard at redhat dot com
2020-11-10 10:22 ` dodji at redhat dot com
2020-11-12 22:23 ` woodard at redhat dot com
2020-11-16 17:15 ` dodji at redhat dot com
2020-11-16 20:33 ` woodard at redhat dot com
2020-11-17 17:39   ` Dodji Seketeli
2020-11-19 10:13   ` Dodji Seketeli
2020-11-17 17:39 ` dodji at seketeli dot org [this message]
2020-11-17 17:50 ` woodard at redhat dot com
2020-11-19 16:56 ` dodji at redhat dot com
2020-11-19 16:58 ` [Bug default/26769] abixml writer misses some member types in the output dodji at redhat dot com
2020-11-20 15:29 ` dodji at redhat dot com
2020-11-20 15:34 ` dodji at redhat dot com
2020-11-20 17:49 ` dodji at seketeli dot org
2020-11-20 22:29 ` woodard at redhat dot com
2020-11-23 12:26 ` dodji at redhat dot com
2020-11-23 17:42 ` woodard at redhat dot com
2020-11-24 10:39 ` 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-26769-9487-SFDKsQE4PM@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).