From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/25456] New: [dwz, low-mem] segfault in die_cu
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <bug-25456-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25456
Bug ID: 25456
Summary: [dwz, low-mem] segfault in die_cu
Product: dwz
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
Segfault in low-mem mode:
...
$ dwz clang-offload-bundler-10.debug
dwz: clang-offload-bundler-10.debug: Couldn't find DIE referenced by
DW_OP_GNU_implicit_pointer
$ dwz clang-offload-bundler-10.debug -l0
Segmentation fault (core dumped)
...
Backtrace:
...
Program received signal SIGSEGV, Segmentation fault.
die_cu (die=0x0) at /data/dwz/dwz.git/dwz.c:984
984 while (!die->die_root)
Missing separate debuginfos, use: zypper install
libelf1-debuginfo-0.168-lp151.4.3.1.x86_64
libz1-debuginfo-1.2.11-lp151.5.3.1.x86_64
(gdb) bt
#0 die_cu (die=0x0) at /data/dwz/dwz.git/dwz.c:984
#1 read_exprloc (dso=dso@entry=0x631660, die=die@entry=0x7fffeeb1efe8,
ptr=0x7ffff270f439 "",
len=<optimized out>, need_adjust=need_adjust@entry=0x7fffffffd29f) at
/data/dwz/dwz.git/dwz.c:1918
#2 0x000000000040e550 in read_loclist (dso=dso@entry=0x631660,
die=die@entry=0x7fffeeb1efe8,
offset=<optimized out>) at /data/dwz/dwz.git/dwz.c:2427
#3 0x000000000040ef75 in checksum_die (dso=<optimized out>, cu=<optimized
out>, top_die=<optimized out>,
die=0x7fffeeb1efe8) at /data/dwz/dwz.git/dwz.c:2672
#4 0x000000000040ea1d in checksum_die (dso=<optimized out>, cu=<optimized
out>, top_die=<optimized out>,
die=0x7fffeeb1f1e0) at /data/dwz/dwz.git/dwz.c:3028
#5 0x000000000040ea1d in checksum_die (dso=<optimized out>, cu=<optimized
out>, top_die=<optimized out>,
die=0x7fffeb7c07f8) at /data/dwz/dwz.git/dwz.c:3028
#6 0x000000000040ea1d in checksum_die (dso=<optimized out>, cu=<optimized
out>, top_die=<optimized out>,
die=0x7fffeb7bee30) at /data/dwz/dwz.git/dwz.c:3028
#7 0x0000000000412e23 in read_debug_info (dso=dso@entry=0x631660,
kind=kind@entry=0,
die_count=die_count@entry=0x400000000) at /data/dwz/dwz.git/dwz.c:6170
#8 0x0000000000413e1f in read_dwarf (dso=dso@entry=0x631660,
quieter=<optimized out>, die_count=0x400000000,
die_count@entry=0x0) at /data/dwz/dwz.git/dwz.c:12066
#9 0x000000000041a4b8 in dwz (file=file@entry=0x7fffffffe106
"clang-offload-bundler-10.debug",
outfile=outfile@entry=0x7fffffffe128 "1", res=res@entry=0x7fffffffdab0,
resa=resa@entry=0x0,
files=files@entry=0x0) at /data/dwz/dwz.git/dwz.c:13629
#10 0x000000000040428c in main (argc=5, argv=<optimized out>) at
/data/dwz/dwz.git/dwz.c:14882
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-01-24 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 0:00 vries at gcc dot gnu.org [this message]
2020-01-01 0:00 ` [Bug default/25456] " vries at gcc dot gnu.org
2020-01-01 0:00 ` vries at gcc dot gnu.org
2020-01-01 0:00 ` vries at gcc dot gnu.org
2020-01-01 0:00 ` [Bug default/25456] [dwz, low-mem, fixed-needs-testcase] " vries at gcc dot gnu.org
2021-03-02 7:59 ` vries at gcc dot gnu.org
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-25456-11298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).