From: "dodji at seketeli dot org" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19596] Incorrect exit status for incompatible ABI change
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-19596-9487-bKKcsJq5hT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19596-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19596
--- Comment #8 from dodji at seketeli dot org ---
I have indeed reproduced this issue and I think it's a real one.
This particular instance of it seems different from the initial one,
though.
I think the current issue is that libabigail considers a removed
function (or global variable) as being an incompatible change, whether
it has been suppressed or not.
Originally, I designed suppression specifications to act on sub-type
changes only, because these were the ones subject to human
interpretation. Removed symbols changes were not meant to be suppressed
because I thought they constitute indubitably incompatible changes.
Of course, real world usage made me revisit that point of view :) But
then some parts of the code were not adjusted as they should have been.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-03-03 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 [Bug default/19596] New: " michi.henning at canonical dot com
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 redhat 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 seketeli dot org [this message]
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-bKKcsJq5hT@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).