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 09:43:15 +0000 [thread overview]
Message-ID: <bug-29901-9487-WsS77s4k0Y@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 |WAITING
--- Comment #4 from dodji at redhat dot com ---
(In reply to Sam James from comment #3)
[...]
> Sorry for the delay!
No problem.
> Here it is (too large to attach to bugzilla, hope
> that's alright):
> https://dev.gentoo.org/~sam/bugs/sourceware/29901/libabigail-bug.tar.xz
I could get it. Thank you.
However, the debug info of each binary (libgs.so.10.00 and libgs.so.10.00.new)
are split out into separate debuginfo files. Those files must be somewhere
(probably under /usr/lib/debug) on your system and are named
"libgs.so.10.00.debug".
I need those debug files to reproduce the issue.
Could you please provide them as well?
Thanks in advance.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-20 9:43 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 [this message]
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-WsS77s4k0Y@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).