From: "jwakely.gcc at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/21296] New: abidiff reports possibly bogus differences and crashes
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <bug-21296-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=21296
Bug ID: 21296
Summary: abidiff reports possibly bogus differences and crashes
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: jwakely.gcc at gmail dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
Created attachment 9935
--> https://sourceware.org/bugzilla/attachment.cgi?id=9935&action=edit
testcase
Using GCC 6 and Clang (any version) to compile the attached code into two
shared libs produces libraries that crash abigail:
clang++ -std=c++14 -o libclang.so -shared -fPIC clanggcc.cxx -g
g++ -o libgcc.so -shared -fPIC clanggcc.cxx -g
abidiff libgcc.so libclang.so
Functions changes summary: 0 Removed (1 filtered out), 2 Changed (9 filtered
out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
2 functions with some indirect sub-type change:
[C]'method STR::~STR(int)' at clanggcc.cxx:6:1 has some indirect sub-type
changes:
linkage names of method STR::~STR(int)
changed from '_ZN3STRD1Ev, _ZN3STRD2Ev' to '_ZN3STRD2Ev'
name of symbol changed from _ZN3STRD1Ev to _ZN3STRD2Ev
parameter 1 of type 'int' was removed
[C]'function std::tuple<STR&&> my_forward_as_tuple<STR>(STR&&)' at
clanggcc.cxx:225:1 has some indirect sub-type changes:
return type changed:
type name changed from 'std::tuple<STR&&>' to 'std::tuple<STR &&>'
type size hasn't changed
1 base class deletion:
struct std::_Tuple_impl<0ul, STR&&> at clanggcc.cxx:119:1
1 base class insertion:
struct std::_Tuple_impl<0, STR &&> at clanggcc.cxx:119:1
abidiff: ../../src/abg-comparison.cc:8205: virtual void
abigail::comparison::fn_parm_diff::report(std::ostream&, const string&) const:
Assertion `get_type_diff() && get_type_diff()->to_be_reported()' failed.
Aborted (core dumped)
If GCC trunk is used instead of GCC 6 then abigail doesn't crash, but still
reports the same diferences, which appear to be bogus.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-03-23 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 jwakely.gcc at gmail dot com [this message]
2017-01-01 0:00 ` Dodji Seketeli
2017-01-01 0:00 ` [Bug default/21296] naive comparison of names of template instantiations leads to false postives dodji at redhat dot com
2017-01-01 0:00 ` [Bug default/21296] abidiff reports possibly bogus differences and crashes dodji at seketeli dot org
2017-01-01 0:00 ` woodard at redhat dot com
2017-01-01 0:00 ` [Bug default/21296] naive comparison of names of template instantiations leads to false postives dodji at redhat dot com
2020-11-12 14:30 ` maennich at android 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-21296-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).