public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28301] libabigail asserts with older versions of gcc / glibc
Date: Mon, 04 Oct 2021 07:55:10 +0000	[thread overview]
Message-ID: <bug-28301-9487-Wb3OMfMnCc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28301-9487@http.sourceware.org/bugzilla/>

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

dodji at redhat dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2021-10-04
     Ever confirmed|0                           |1

--- Comment #4 from dodji at redhat dot com ---
(In reply to Seppo Yli-Olli from comment #3)
> Okay. So I just reproduced same asserts with by staging our ABI image twice
> (identical files) in and running ABI checker between them. Since bunch of
> these files seem to be present in glibc, added
> https://nanonyme.kapsi.fi/public/glibc.tar.xz here. I'm not sure if I should
> be uploading this large packages into the bugzilla.

Hello.

For me to reproduce the issue and be able to debug it, it's helpful to provide
a command line to reproduce the issue, like 'abidiff binary1 binary2'.

I have downloaded the tarball at https://nanonyme.kapsi.fi/public/glibc.tar.xz.
 Thank you for having provided it.  But then, how am I supposed to reproduce
the problem exactly?

Also, have you tried to reproduce the issue using libabigail from the master
repository?

The libabigail version from master could handle the binaries from the tarball
that your version of libabigail was failing from, if I believe one of the
comments of the bug.  Here is what I did with the current libabigail from
master to test for that:

$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libanl.so.1
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libnsl.so.1
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libpthread.so.0
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libpthread.so.0
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libcrypt.so.1
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libutil.so.1
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libdl.so.2
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libnss_db.so.2
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/gconv/libJISX0213.so
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libnss_files.so.2
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libnss_hesiod.so.2
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libnss_compat.so.2
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libthread_db.so.1
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libc.so.6
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/librt.so.1
$ abidw --abidiff glibc/usr/lib/x86_64-linux-gnu/libresolv.so.2
$

I think that I really need to release what we have in master now so that you
can update to that one instead as there are many many fixes stacked there.

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

  parent reply	other threads:[~2021-10-04  7:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 12:52 [Bug default/28301] New: " jjardon at gnome dot org
2021-09-02 12:55 ` [Bug default/28301] " gprocida at google dot com
2021-09-02 14:06 ` jjardon at gnome dot org
2021-10-01 20:37 ` seppo.yliolli at gmail dot com
2021-10-04  7:55 ` dodji at redhat dot com [this message]
2021-10-04  8:08 ` seppo.yliolli at gmail dot com
2021-10-04 11:20 ` seppo.yliolli at gmail dot com
2021-10-07  7:51 ` dodji at redhat dot com
2021-10-07  8:44 ` seppo.yliolli at gmail dot com
2022-03-28 18:59 ` seppo.yliolli at gmail dot com
2023-04-24 14:49 ` ben at demerara dot io
2023-04-26 14:13 ` 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-28301-9487-Wb3OMfMnCc@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).