From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19036] New: abixml symmetry broken by loss of private attribute
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <bug-19036-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=19036
Bug ID: 19036
Summary: abixml symmetry broken by loss of private attribute
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
Created attachment 8659
--> https://sourceware.org/bugzilla/attachment.cgi?id=8659&action=edit
ELF object that reproduces the above problem
hype260@ben:less
\\_collab\\_usr\\_global\\_tools\\_order\\_spack\\_opt\\_chaos_5_x86_64_ib\\_gcc\@4.4.7\\_vtk\@6.1.0-2f431570\\_lib\\_libvtkInfovisCore-6.1.so/stderr
Functions changes summary: 0 Removed, 8 Changed, 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
<snip a bunch of cases of loss of reference see: pr19035>
[C]'method bool vtkVariant::operator<(const vtkVariant&)' has some indirect
sub-type changes:
'method bool vtkVariant::operator<(const vtkVariant&)' access changed from
'private' to 'public'
The loss of private attribute is something different than I've seen elsewhere.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-09-30 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 woodard at redhat dot com [this message]
2015-01-01 0:00 ` [Bug default/19036] " woodard at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2015-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-19036-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).