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/29901] abidiff hangs when comparing freshly-built libgs.so.10 with itself (runs for hours)
Date: Tue, 20 Dec 2022 15:37:57 +0000	[thread overview]
Message-ID: <bug-29901-9487-eVpQbd5wZD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29901-9487@http.sourceware.org/bugzilla/>

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

dodji at redhat dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from dodji at redhat dot com ---
This problem should hopefully be fixed by commit
https://sourceware.org/git/?p=libabigail.git;a=commit;h=e1aadfa576963f2baddc6b6bf17898a86e3a041e.

On my machine, the comparison now ends up in about less than 45minutes.  This
is still a lot, but at least there is no more infinite loop.

This fix should be available in libabigail 2.3.

Thank you taking the time to report this problem and sorry for the
inconvenience.

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

      parent reply	other threads:[~2022-12-20 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  4:05 [Bug default/29901] New: " sam at gentoo dot org
2022-12-16  8:14 ` [Bug default/29901] " sam at gentoo dot org
2022-12-19 17:05 ` dodji at redhat dot com
2022-12-20  8:40 ` sam at gentoo dot org
2022-12-20  9:43 ` dodji at redhat dot com
2022-12-20  9:52 ` sam at gentoo dot org
2022-12-20 11:25 ` dodji at redhat dot com
2022-12-20 15:37 ` dodji at redhat dot com [this message]

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-29901-9487-eVpQbd5wZD@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).