From: "michi.henning at canonical dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19596] New: Incorrect exit status for incompatible ABI change
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-19596-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=19596
Bug ID: 19596
Summary: Incorrect exit status for incompatible ABI change
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: michi.henning at canonical dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
Created attachment 8969
--> https://sourceware.org/bugzilla/attachment.cgi?id=8969&action=edit
Dump files and report file
I just swapped the order of two pure virtual methods in an abstract base class.
The generated report correctly diagnoses the ABI break, but the exit status
from abidiff is 4. I was expecting 8 or 12.
Here is the trace from my build driver script:
+ abidiff libunity-scopes_1.0.0.abi.xml libunity-scopes_1.0.3.abi.xml
check-abi-compliance.sh: ABI is compatible with changes, see
libunity-scopes_1.0.3_abi-report.txt for details.
+ status=4
+ [ 4 -ge 8 ]
+ [ 4 -ge 4 ]
+ echo check-abi-compliance.sh: ABI is compatible with changes, see
libunity-scopes_1.0.3_abi-report.txt for details.
+ exit 0
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-02-10 10:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 michi.henning at canonical dot com [this message]
2016-01-01 0:00 ` [Bug default/19596] " michi.henning at canonical dot com
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` michi.henning at canonical dot com
2016-01-01 0:00 ` dodji at seketeli dot org
2016-01-01 0:00 ` michi.henning at canonical dot com
2016-01-01 0:00 ` dodji at seketeli dot org
2016-01-01 0:00 ` Dodji Seketeli
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` michi.henning at canonical dot com
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` dodji at seketeli dot org
2016-01-01 0:00 ` 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-19596-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).