public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29673] qt6-qtbase from f37 fails fedabipkgdiff --self-compare
Date: Fri, 14 Oct 2022 17:14:36 +0000	[thread overview]
Message-ID: <bug-29673-9487-E2I6m0KDAx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29673-9487@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29673

--- Comment #2 from Ben Woodard <woodard at redhat dot com> ---
crash, enlightenment, elrlang-erts and bpftrace seem to be manifestations of
similar problems.

Comparing the ABI of binaries between crash-8.0.1-3.fc37.s390x.rpm and
crash-8.0.1-3.fc37.s390x.rpm:

======== comparing'crash' to itself wrongly yielded result: ===========
  Functions changes summary: 0 Removed, 1 Changed, 0 Added function
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

  1 function with some indirect sub-type change:

    [C] 'function regcache* get_thread_regcache(thread_info*)' at
regcache.c:408:1 has some indirect sub-type changes:

===SELF CHECK FAILED for 'crash'

-----------------

--------------

Comparing the ABI of binaries between enlightenment-0.25.4-1.fc37.aarch64.rpm
and enlightenment-0.25.4-1.fc37.aarch64.rpm:

======== comparing'enlightenment' to itself wrongly yielded result: ===========
  Functions changes summary: 0 Removed, 0 Changed (238 filtered out), 0 Added
functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

===SELF CHECK FAILED for 'enlightenment'

------------------

Comparing the ABI of binaries between erlang-erts-25.1.1-1.fc37.ppc64le.rpm and
erlang-erts-25.1.1-1.fc37.ppc64le.rpm:

======== comparing'beam.smp' to itself wrongly yielded result: ===========
  Functions changes summary: 0 Removed, 0 Changed (1322 filtered out), 0 Added
functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

===SELF CHECK FAILED for 'beam.smp'

------------------

Comparing the ABI of binaries between gimp-2.10.32-3.fc37.i686.rpm and
gimp-2.10.32-3.fc37.i686.rpm:

==== SELF CHECK SUCCEEDED for 'gimp-2.10' ====
======== comparing'gimp-console-2.10' to itself wrongly yielded result:
===========
  Functions changes summary: 0 Removed, 0 Changed (5 filtered out), 0 Added
functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

===SELF CHECK FAILED for 'gimp-console-2.10'

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-10-14 17:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 22:26 [Bug default/29673] New: " woodard at redhat dot com
2022-10-11 22:27 ` [Bug default/29673] " woodard at redhat dot com
2022-10-14 17:02 ` woodard at redhat dot com
2022-10-14 17:14 ` woodard at redhat dot com [this message]
2022-10-14 17:23 ` woodard at redhat dot com
2022-10-14 17:28 ` woodard at redhat dot com
2022-10-14 17:33 ` woodard at redhat dot com
2022-10-14 18:32 ` woodard at redhat dot com
2022-12-16 21:58 ` woodard at redhat dot com
2023-01-07  3:08 ` woodard at redhat dot com
2023-03-23 22:01 ` woodard at redhat dot com
2023-03-27 20:08 ` woodard at redhat dot com
2023-05-18 20:23 ` woodard at redhat dot com
2023-05-18 22:17 ` woodard 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-29673-9487-E2I6m0KDAx@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).