From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26908] abidw --abidiff /lib64/libclang-cpp.so.11 crashes in dwarf_dieoffset
Date: Mon, 16 Nov 2020 21:17:26 +0000 [thread overview]
Message-ID: <bug-26908-9487-aEjdaGq7B2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26908-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26908
--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
Program received signal SIGSEGV, Segmentation fault.
dwarf_diecu (die=0x7fffffffd540, result=0x7fffffffd560, address_sizep=0x0,
offset_sizep=0x0) at libdwP.h:947
Downloading source file
/usr/src/debug/elfutils-0.182-1.fc33.x86_64/libdw/libdwP.h...
947 return cu->sec_idx;
This one is from /lib64/libclang.so.11 also from
clang-libs-11.0.0-2.fc33.x86_64
Even though the backtrace is different at level 0 and 1, #2 is the same.
#0 dwarf_diecu (die=0x7fffffffd540, result=0x7fffffffd560, address_sizep=0x0,
offset_sizep=0x0) at libdwP.h:947
#1 0x00007ffff7ef1e74 in
abigail::dwarf_reader::imported_unit_point::imported_unit_point
(from=4294956352, imported_die=..., import_off=<optimized out>,
this=0x7fffffffd580) at ../../../libabigail/src/abg-dwarf-reader.cc:271
#2 abigail::dwarf_reader::read_context::build_die_parent_relations_under
(this=0x442c40, die=0x7fffffffd650,
source=abigail::dwarf_reader::PRIMARY_DEBUG_INFO_DIE_SOURCE,
imported_units=std::vector of length 0, capacity 0) at
../../../libabigail/src/abg-dwarf-reader.cc:7686
#3 0x00007ffff7ef22ab in
abigail::dwarf_reader::read_context::build_die_parent_maps
(this=this@entry=0x442c40) at ../../../libabigail/src/abg-dwarf-reader.cc:7819
#4 0x00007ffff7ee4d57 in abigail::dwarf_reader::read_debug_info_into_corpus
(ctxt=...) at ../../../libabigail/src/abg-dwarf-reader.cc:15895
#5 abigail::dwarf_reader::read_corpus_from_elf (ctxt=...,
status=@0x7fffffffd80c: abigail::dwarf_reader::STATUS_UNKNOWN) at
../../../libabigail/src/abg-dwarf-reader.cc:17149
#6 0x0000000000405c93 in load_corpus_and_write_abixml (opts=...,
context=std::shared_ptr<abigail::dwarf_reader::read_context> (use count 1, weak
count 0) = {...}, env=std::shared_ptr<abigail::ir::environment> (use count 1,
weak count 0) = {...}, argv=0x7fffffffdd58) at
../../../libabigail/tools/abidw.cc:494
#7 main (argc=<optimized out>, argv=0x7fffffffdd58) at
../../../libabigail/tools/abidw.cc:866
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-16 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 20:43 [Bug default/26908] New: " woodard at redhat dot com
2020-11-16 21:17 ` woodard at redhat dot com [this message]
2020-11-21 0:34 ` [Bug default/26908] " woodard at redhat dot com
2020-11-23 17:51 ` woodard at redhat dot com
2020-11-28 20:51 ` dodji at redhat dot com
2020-11-30 6:12 ` [Bug default/26908] libabigail's dwarf reader crashes while scanning a DW_TAG_partial_unit with no child node 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-26908-9487-aEjdaGq7B2@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).