From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30307] arch specific self compare problem with bpftrace
Date: Mon, 03 Apr 2023 17:30:35 +0000 [thread overview]
Message-ID: <bug-30307-9487-2tXh98J7BS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30307-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30307
--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
btrfs-progs has a similar arch specific error. However, instead of affecting
s390x it affects ppc64le:
Comparing the ABI of binaries between btrfs-progs-6.2.2-1.fc37.ppc64le.rpm and
btrfs-progs-6.2.2-1.fc37.ppc64le.rpm:
======== comparing'btrfs' to itself wrongly yielded result: ===========
Functions changes summary: 0 Removed, 0 Changed (62 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
===SELF CHECK FAILED for 'btrfs'
==== SELF CHECK SUCCEEDED for 'btrfs-convert' ====
==== SELF CHECK SUCCEEDED for 'mkfs.btrfs' ====
======== comparing'btrfs-image' to itself wrongly yielded result: ===========
Functions changes summary: 0 Removed, 0 Changed (61 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
===SELF CHECK FAILED for 'btrfs-image'
======== comparing'btrfstune' to itself wrongly yielded result: ===========
Functions changes summary: 0 Removed, 0 Changed (61 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
===SELF CHECK FAILED for 'btrfstune'
======== comparing'btrfs-map-logical' to itself wrongly yielded result:
===========
Functions changes summary: 0 Removed, 0 Changed (61 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
===SELF CHECK FAILED for 'btrfs-map-logical'
======== comparing'btrfs-select-super' to itself wrongly yielded result:
===========
Functions changes summary: 0 Removed, 0 Changed (61 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
===SELF CHECK FAILED for 'btrfs-select-super'
======== comparing'btrfs-find-root' to itself wrongly yielded result:
===========
Functions changes summary: 0 Removed, 0 Changed (61 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
===SELF CHECK FAILED for 'btrfs-find-root'
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-03 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 17:28 [Bug default/30307] New: " woodard at redhat dot com
2023-04-03 17:30 ` woodard at redhat dot com [this message]
2023-04-03 17:35 ` [Bug default/30307] " woodard at redhat dot com
2023-04-03 17:42 ` woodard at redhat dot com
2023-04-03 17:48 ` [Bug default/30307] " woodard at redhat dot com
2023-04-03 22:10 ` woodard at redhat dot com
2023-04-26 12:38 ` 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-30307-9487-2tXh98J7BS@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).