From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30329] abidiff assertion error in dwarf reader
Date: Tue, 11 Apr 2023 09:04:29 +0000 [thread overview]
Message-ID: <bug-30329-9487-M2Ti6RmwmF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30329-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30329
--- Comment #2 from dodji at redhat dot com ---
Hello,
I could not reproduce the issue because there is some debuginfo missing from
the tarball you submitted.
For instance, in the libsqlite3 tarball, the debug info that is missing is
{new,old}-image/usr/lib/debug/dwz/components/sqlite.bst/x86_64-unknown-linux-gnu.
It's called an 'alternate debuginfo file'.
That debug info file is referenced by the main debuginfo file
{new,old}-image/usr/lib/debug/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.debug.
Could you please provide an updated tarball with that alternate debug info file
in?
Thank you for taking 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.
next prev parent reply other threads:[~2023-04-11 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 14:10 [Bug default/30329] New: " ben at demerara dot io
2023-04-11 7:41 ` [Bug default/30329] " ben at demerara dot io
2023-04-11 9:04 ` dodji at redhat dot com [this message]
2023-04-11 9:33 ` ben at demerara dot io
2023-04-11 10:43 ` Dodji Seketeli
2023-04-11 10:44 ` dodji at seketeli dot org
2023-04-12 8:53 ` ben at demerara dot io
2023-04-12 8:55 ` ben at demerara dot io
2023-04-25 10:17 ` dodji at redhat dot com
2023-04-25 14:00 ` dodji at redhat dot com
2023-04-25 14:03 ` ben at demerara dot io
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-30329-9487-M2Ti6RmwmF@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).