public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dodji at seketeli dot org" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19707] Weird report for subtype change and "no data member change"
Date: Fri, 01 Jan 2016 00:00:00 -0000	[thread overview]
Message-ID: <bug-19707-9487-cWqR874pk6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19707-9487@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=19707

--- Comment #1 from dodji at seketeli dot org ---
Hello,

> The other puzzling thing is this:
>
>   [C]'method unity::scopes::ActivationQueryBase::ActivationQueryBase(const
> unity::scopes::Result&, const unity::scopes::ActionMetadata&)' at
> ActivationQueryBase.cpp:29:1 has some indirect sub-type changes:
>     parameter 1 of type 'const unity::scopes::Result&' has sub-type changes:
>       in referenced type 'const unity::scopes::Result':
>         in unqualified underlying type 'class unity::scopes::Result' at
> Result.h:50:1:
>           no data member change (1 filtered);

I believe this is a bug.  The comparison engine noticed a change that
was later flagged as "non serious" on a data member of
unity::scope::Result.  And thus, that change was filtered out.  But
then, as this is the only sub-type change seen on the function
ActivationQueryBase::ActivationQueryBase() (and as this only change got
filtered out) the entire change report on that function should have been
filtered out.

In other words, in libabigail parlance, I believe this is a
categorization propagation bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2016-02-23  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01  0:00 [Bug default/19707] New: " michi.henning at canonical dot com
2016-01-01  0:00 ` [Bug default/19707] " dodji at seketeli dot org
2016-01-01  0:00 ` dodji at seketeli dot org [this message]
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 redhat dot com
2016-01-01  0:00 ` [Bug default/19707] New: " Dodji Seketeli
2016-01-01  0:00 ` Dodji Seketeli
2016-01-01  0:00 ` [Bug default/19707] " 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-19707-9487-cWqR874pk6@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).