From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26943] New: inexplicable type changing when running abidiff
Date: Wed, 25 Nov 2020 01:24:47 +0000 [thread overview]
Message-ID: <bug-26943-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26943
Bug ID: 26943
Summary: inexplicable type changing when running abidiff
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: ---
With commit 2c0dd017 from dodji/PR26769
This one seems really unique. It appears that two types are inexplicably
changing in a way that is not clearly reported.
$ rpm -qf /lib64/libQtCore.so.4.8.7
qt-4.8.7-57.fc33.x86_64
$ abidw --abidiff /lib64/libQtCore.so.4.8.7
$ echo $?
0
$ abidw /lib64/libQtCore.so.4.8.7 > libQtCore.so.4.8.7.abixml
$ abidiff --harmless libQtCore.so.4.8.7.abixml /lib64/libQtCore.so.4.8.7
Functions changes summary: 0 Removed, 43 Changed, 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
43 functions with some indirect sub-type change:
[C] 'method QTextCodec* QSettings::iniCodec() const' at qsettings.cpp:2997:1
has some indirect sub-type changes:
return type changed:
in pointed to type 'class QTextCodec' at qtextcodec.h:62:1:
[C] 'method void QSettings::setIniCodec(QTextCodec*)' at qsettings.cpp:2966:1
has some indirect sub-type changes:
parameter 1 of type 'QTextCodec*' changed:
in pointed to type 'class QTextCodec' at qtextcodec.h:62:1:
[C] 'method QTextCodec* QTextStream::codec() const' at qtextstream.cpp:3006:1
has some indirect sub-type changes:
return type changed:
in pointed to type 'class QTextCodec' at qtextcodec.h:62:1:
[C] 'method void QTextStream::setCodec(QTextCodec*)' at
qtextstream.cpp:2968:1 has some indirect sub-type changes:
parameter 1 of type 'QTextCodec*' changed:
in pointed to type 'class QTextCodec' at qtextcodec.h:62:1:
[C] 'method QXmlStreamWriter::QXmlStreamWriter(QByteArray*)' at
qxmlstream.h:423:1 has some indirect sub-type changes:
implicit parameter 0 of type 'QXmlStreamWriter*' has sub-type changes:
in pointed to type 'class QXmlStreamWriter' at qxmlstream.h:416:1:
type size hasn't changed
1 data member change:
type of 'QScopedPointer<QXmlStreamWriterPrivate,
QScopedPointerDeleter<QXmlStreamWriterPrivate> > QXmlStreamWriter::d_ptr'
changed:
type size hasn't changed
1 data member change:
type of 'QXmlStreamWriterPrivate*
QScopedPointer<QXmlStreamWriterPrivate,
QScopedPointerDeleter<QXmlStreamWriterPrivate> >::d' changed:
in pointed to type 'class QXmlStreamWriterPrivate' at
qxmlstream.cpp:2960:1:
type size hasn't changed
2 data member changes:
type of 'QXmlStreamWriter* QXmlStreamWriterPrivate::q_ptr'
changed:
pointed to type 'class QXmlStreamWriter' changed, as
being reported
type of 'QTextCodec* QXmlStreamWriterPrivate::codec'
changed:
in pointed to type 'class QTextCodec' at
qtextcodec.h:62:1:
<snip redundant reporting>
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-11-25 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 1:24 woodard at redhat dot com [this message]
2020-11-28 11:11 ` [Bug default/26943] " 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-26943-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).