From: "szhorvat at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27699] New: Assertion failure on armv7l
Date: Tue, 06 Apr 2021 06:40:51 +0000 [thread overview]
Message-ID: <bug-27699-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27699
Bug ID: 27699
Summary: Assertion failure on armv7l
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: szhorvat at gmail dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
I am using abidw on a Raspberry Pi 4, Raspbian Buster. When I compile the
igraph project (https://github.com/igraph/igraph/) in debug mode, with
link-time optimization, into a shared library, and call
abidw src/libigraph.so
it crashes with the following:
abidw: abg-dwarf-reader.cc:13241: void
abigail::dwarf_reader::finish_member_function_reading(Dwarf_Die*, const
function_decl_sptr&, const class_or_union_sptr&,
abigail::dwarf_reader::read_context&): Assertion `__abg_cond__' failed.
This is libabigail 1.8.0 that I compiled myself from sources. However, the same
crash happens also with libabigail 1.5.0 which is included in Raspbian Buster.
It only happens when I compile this project with link-time optimization.
Compiler is: gcc (Raspbian 8.3.0-6+rpi1) 8.3.0
I cannot reproduce the same issue on Ubuntu 20.04 on x86_64.
I am happy to provide the .so file, or more specific information about how I
compiled igraph to obtain the offending .so file.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-04-06 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 6:40 szhorvat at gmail dot com [this message]
2021-04-06 9:06 ` [Bug default/27699] " maennich at android dot com
2021-04-06 17:13 ` szhorvat at gmail 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-27699-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).