From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30307] New: arch specific self compare problem with bpftrace
Date: Mon, 03 Apr 2023 17:28:03 +0000 [thread overview]
Message-ID: <bug-30307-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30307
Bug ID: 30307
Summary: arch specific self compare problem with bpftrace
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
This is being split off from 29673 because I do not think that this is the same
bug.
This was with the latest trunk.
Note that this problem only seems to occur for s390x
fedabipkgdiff --self-compare -a --from fc37 bpftrace
Comparing the ABI of binaries between bpftrace-0.16.0-3.fc37.aarch64.rpm and
bpftrace-0.16.0-3.fc37.aarch64.rpm:
==== SELF CHECK SUCCEEDED for 'bpftrace' ====
==== SELF CHECK SUCCEEDED for 'bpftrace-aotrt' ====
Comparing the ABI of binaries between bpftrace-0.16.0-3.fc37.ppc64le.rpm and
bpftrace-0.16.0-3.fc37.ppc64le.rpm:
==== SELF CHECK SUCCEEDED for 'bpftrace' ====
==== SELF CHECK SUCCEEDED for 'bpftrace-aotrt' ====
Comparing the ABI of binaries between bpftrace-0.16.0-3.fc37.s390x.rpm and
bpftrace-0.16.0-3.fc37.s390x.rpm:
======== comparing'bpftrace' to itself wrongly yielded result: ===========
Functions changes summary: 0 Removed, 0 Changed (96 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added
variable
===SELF CHECK FAILED for 'bpftrace'
======== comparing'bpftrace-aotrt' to itself wrongly yielded result:
===========
Functions changes summary: 0 Removed, 0 Changed (96 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added
variable
===SELF CHECK FAILED for 'bpftrace-aotrt'
Comparing the ABI of binaries between bpftrace-0.16.0-3.fc37.x86_64.rpm and
bpftrace-0.16.0-3.fc37.x86_64.rpm:
==== SELF CHECK SUCCEEDED for 'bpftrace' ====
==== SELF CHECK SUCCEEDED for 'bpftrace-aotrt' ====
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-04-03 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 17:28 woodard at redhat dot com [this message]
2023-04-03 17:30 ` [Bug default/30307] " woodard at redhat dot com
2023-04-03 17:35 ` 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@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).