From: "dermojo at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29733] New: Comparing 2.0 dump to 2.1 dump: parameter 1 of type 'int' was added to destructor
Date: Mon, 31 Oct 2022 08:41:31 +0000 [thread overview]
Message-ID: <bug-29733-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29733
Bug ID: 29733
Summary: Comparing 2.0 dump to 2.1 dump: parameter 1 of type
'int' was added to destructor
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: dermojo at gmail dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
Created attachment 14423
--> https://sourceware.org/bugzilla/attachment.cgi?id=14423&action=edit
sample library code
Hi,
I'm storing ABI dumps together with my shared library (C++) to check for ABI
breaks when rebuilding. I found an incompatibility when upgrading libabigail
and its tools from 2.0 to 2.1:
The exact same code yields different ABI dumps between both versions, and
abidiff reports incompatible changes, For example, the attached sample shows
this (compiled with "g++ -shared -o libsample.so sample.cpp -Wall -std=c++11 -g
-ggdb"):
> $ ~/git/libabigail-2.1/build/tools/abidiff abi-2.0.dump abi-2.1.dump
> 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] 'method Sample::~Sample()' at sample.cpp:2:1 has some indirect sub-type changes:
> parameter 1 of type 'int' was added
>
> (exit code: 4)
Comparing the ABI dumps between version 2.0 and 2.1, I can see that the 2.0
dump only contains 1 destructor as member function (_ZN6SampleD2Ev), while the
2. dump contains an additional _ZN6SampleD4Ev and both have the additional
"int" parameter.
The library symbol table doesn't contain _ZN6SampleD4Ev, only the debug info
does, and AFAIS only the D4 destructor has the additional int parameter.
Any help to resolve this is highly appreitated.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-31 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 8:41 dermojo at gmail dot com [this message]
2022-10-31 8:42 ` [Bug default/29733] " dermojo at gmail dot com
2022-10-31 8:42 ` dermojo at gmail dot com
2022-12-01 11:09 ` 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-29733-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).