From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29901] New: abidiff hangs when comparing freshly-built libgs.so.10 with itself (runs for hours)
Date: Fri, 16 Dec 2022 04:05:01 +0000 [thread overview]
Message-ID: <bug-29901-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29901
Bug ID: 29901
Summary: abidiff hangs when comparing freshly-built libgs.so.10
with itself (runs for hours)
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: sam at gentoo dot org
CC: libabigail at sourceware dot org
Target Milestone: ---
Created attachment 14519
--> https://sourceware.org/bugzilla/attachment.cgi?id=14519&action=edit
backtrace from hanging (few minutes)
Sorry for the lack of detail, I'm not sure how to describe this properly yet.
In Gentoo, we have tooling for developers to use abidiff when upgrading
packages or changing build options, which is a great convenience. It compares
the system copy with the version just built. Thanks for libabigail, it's a huge
help.
With ghostscript-gpl-10.0.0, libabigail's abidiff seems to hang when doing this
comparison (had been running for an hour at this point):
```
root 2761321 97.6 1.8 1360832 1242480 pts/1 RN+ 02:40 55:22 abidiff
--stats --d1 /usr/lib/debug --d2
/var/tmp/portage/app-text/ghostscript-gpl-10.0.0-r4/image/usr/lib/debug
/usr/lib64/libgs.so.10.00
/var/tmp/portage/app-text/ghostscript-gpl-10.0.0-r4/image/usr/lib64/libgs.so.10.00
```
Same happens without --stats.
$ abidiff --version
abidiff: 2.2.0
Attached backtrace after running for about 3-4 minutes on a fresh run. Sorry
it's not from a longer run, I can grab one of those if needed. Let me know if &
how to grab more info. Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-12-16 4:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 4:05 sam at gentoo dot org [this message]
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
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@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).