From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27236] New: self comparison failed on libbfdo.so from package binutils-2.35-18.fc33.ppc64le.rpm
Date: Mon, 25 Jan 2021 09:51:04 +0000 [thread overview]
Message-ID: <bug-27236-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27236
Bug ID: 27236
Summary: self comparison failed on libbfdo.so from package
binutils-2.35-18.fc33.ppc64le.rpm
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: dodji at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
After extracting the content of packages binutils-2.35-18.fc33.ppc64le.rpm and
binutils-debuginfo-2.35-18.fc33.ppc64le.rpm, here is what abidw --abidiff is
saying:
$ abidw --abidiff -d usr/lib/debug usr/lib64/libbfd-2.35-18.fc33.so
Functions changes summary: 0 Removed, 4 Changed, 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
4 functions with some indirect sub-type change:
[C] 'function char* xcoff64_core_file_failing_command(bfd*)' at
aix5ppc-core.c:345:1 has some indirect sub-type changes:
parameter 1 of type 'bfd*' has sub-type changes:
in pointed to type 'struct bfd' at bfd.h:6488:1:
type size hasn't changed
9 data member changes:
type of 'bfd* bfd::lru_prev' changed:
pointed to type 'struct bfd' changed, as being reported
type of 'bfd* bfd::lru_next' changed:
pointed to type 'struct bfd' changed, as being reported
type of 'bfd* bfd::plugin_dummy_bfd' changed:
pointed to type 'struct bfd' changed, as being reported
type of 'bfd_symbol** bfd::outsymbols' changed:
in pointed to type 'bfd_symbol*':
in pointed to type 'struct bfd_symbol' at bfd.h:6278:1:
type size hasn't changed
1 data member change:
type of 'bfd* bfd_symbol::the_bfd' changed:
pointed to type 'struct bfd' changed, as being reported
type of 'bfd* bfd::my_archive' changed:
pointed to type 'struct bfd' changed, as being reported
type of 'bfd* bfd::archive_next' changed:
pointed to type 'struct bfd' changed, as being reported
type of 'bfd* bfd::archive_head' changed:
pointed to type 'struct bfd' changed, as being reported
type of 'bfd* bfd::nested_archives' changed:
pointed to type 'struct bfd' changed, as being reported
type of 'union {bfd* next; bfd_link_hash_table* hash;} bfd::link'
changed:
type size hasn't changed
1 data member change:
type of 'bfd* next' changed:
pointed to type 'struct bfd' changed, as being reported
type changed from:
union {bfd* next; bfd_link_hash_table* hash;}
to:
union {bfd* next; bfd_link_hash_table* hash;}
[C] 'function int xcoff64_core_file_failing_signal(bfd*)' at
aix5ppc-core.c:351:1 has some indirect sub-type changes:
parameter 1 of type 'bfd*' has sub-type changes:
pointed to type 'struct bfd' changed at bfd.h:6488:1, as reported earlier
[C] 'function bfd_boolean xcoff64_core_file_matches_executable_p(bfd*, bfd*)'
at aix5ppc-core.c:339:1 has some indirect sub-type changes:
parameter 1 of type 'bfd*' has sub-type changes:
pointed to type 'struct bfd' changed at bfd.h:6488:1, as reported earlier
parameter 2 of type 'bfd*' has sub-type changes:
pointed to type 'struct bfd' changed at bfd.h:6488:1, as reported earlier
[C] 'function bfd_cleanup xcoff64_core_p(bfd*)' at aix5ppc-core.c:332:1 has
some indirect sub-type changes:
parameter 1 of type 'bfd*' has sub-type changes:
pointed to type 'struct bfd' changed at bfd.h:6488:1, as reported earlier
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-01-25 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 9:51 dodji at redhat dot com [this message]
2021-01-25 9:54 ` [Bug default/27236] " dodji at redhat dot com
2021-01-26 3:55 ` 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-27236-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).