From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19846] New: variable decl associated with the wrong debug info section
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-19846-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=19846
Bug ID: 19846
Summary: variable decl associated with the wrong debug info
section
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: dodji at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
$ abipkgdiff --d1 boost-debuginfo-1.53.0-18.el7.x86_64.rpm --d2
boost-debuginfo-1.53.0-25.el7.x86_64.rpm
boost-serialization-1.53.0-18.el7.x86_64.rpm
boost-serialization-1.53.0-25.el7.x86_64.rpm
lt-abipkgdiff: /home/dodji/git/libabigail/master/src/abg-dwarf-reader.cc:7546:
abigail::ir::qualified_type_def_sptr
abigail::dwarf_reader::build_qualified_type(abigail::dwarf_reader::read_context&,
Dwarf_Die*, bool, bool, size_t): Assertion `utype' failed.
Abandon (core dumped)
$
What is happening here is that the decl of a member variable which DIE is in
the main debug info section is wrongly being associated with the alternate
debug info section, just because the specification DIE of that member variable
happens to be in the alternate debug info section.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-03-18 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 dodji at redhat dot com [this message]
2016-01-01 0:00 ` [Bug default/19846] " 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-19846-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).