From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 71468 invoked by alias); 23 Feb 2016 08:25:40 -0000 Mailing-List: contact libabigail-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: Sender: libabigail-owner@sourceware.org Received: (qmail 71405 invoked by uid 55); 23 Feb 2016 08:25:37 -0000 From: "dodji at seketeli dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: libabigail X-Bugzilla-Component: default X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dodji at seketeli dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dodji at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2016-q1/txt/msg00137.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D19707 --- 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 chang= es: > 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. --=20 You are receiving this mail because: You are on the CC list for the bug.