public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19026] New: ABI symmetry problems and an assert with libparseAPI.so
Date: Thu, 01 Jan 2015 00:00:00 -0000	[thread overview]
Message-ID: <bug-19026-9487@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 19026
           Summary: ABI symmetry problems and an assert with
                    libparseAPI.so
           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 8648
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8648&action=edit
reproducing ELF file.

hype356@ben:~/bin/abidw --abidiff
/collab/usr/global/tools/order/spack/opt/chaos_5_x86_64_ib/gcc@4.4.7/dyninst@8.1.2-b04
^M0c20e/lib/libparseAPI.so
Functions changes summary: 0 Removed, 19 Changed, 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

19 functions with some indirect sub-type change:

  [C]'method virtual Dyninst::ASTVisitor::ASTPtr
Dyninst::ASTVisitor::visit(Dyninst::DataflowAPI::ConstantAST*)' has some
indirect sub-type changes:
    return type changed:
      typedef name changed from Dyninst::ASTVisitor::ASTPtr to
Dyninst::DataflowAPI::BooleanVisitor::ASTPtr

<snip>

  [C]'method virtual const std::string Dyninst::DataflowAPI::RoseAST::format()'
has some indirect sub-type changes:
    return type changed:
      in unqualified underlying type 'typedef std::string':
        underlying type 'struct std::basic_string<char, std::char_traits<char>,
std::allocator<char> >' changed:
          1 data member change:
abidw: ../../src/abg-comparison.cc:10185: abigail::comparison::base_diff_sptr
abigail::comparison::compute_diff(abigail::ir::class_decl::base_spec_sptr,
abigail::ir::class_decl::base_spec_sptr,
abigail::comparison::diff_context_sptr): Assertion `first->get_environment() ==
second->get_environment()' failed.
Aborted (core dumped)

This looks like a different assert than the other one. Also some ABI
information must not be being properly stored due to the fact that there are a
lot of ABI symmetry problems.

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

             reply	other threads:[~2015-09-29 21:06 UTC|newest]

Thread overview: 12+ 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/19026] ODR optimization considers types with same name and different size to be equivalent woodard at redhat dot com
2015-01-01  0:00 ` [Bug default/19026] ABI symmetry problems and an assert with libparseAPI.so woodard at redhat dot com
2015-01-01  0:00 ` [Bug default/19026] ODR optimization considers types with same name and different size to be equivalent dodji at redhat dot com
2015-01-01  0:00 ` [Bug default/19026] ABI symmetry problems and an assert with libparseAPI.so woodard at redhat dot com
2015-01-01  0:00 ` woodard at redhat dot com
2015-01-01  0:00 ` woodard at redhat dot com
2015-01-01  0:00 ` [Bug default/19026] ODR optimization considers types with same name and different size to be equivalent dodji at redhat dot com
2015-01-01  0:00 ` woodard at redhat dot com
2015-01-01  0:00 ` [Bug default/19026] ABI symmetry problems and an assert with libparseAPI.so dodji at redhat dot com
2015-01-01  0:00 ` woodard at redhat dot com
2015-01-01  0:00 ` [Bug default/19026] ODR optimization considers types with same name and different size to be equivalent 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-19026-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).