public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/27893] New: [fission] segfault in dw2_expand_symtabs_matching_one
Date: Thu, 20 May 2021 19:57:31 +0000 [thread overview]
Message-ID: <bug-27893-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27893
Bug ID: 27893
Summary: [fission] segfault in dw2_expand_symtabs_matching_one
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: symtab
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
When running test-case gdb.base/jit-elf-so.exp with target board fission, I run
into:
...
(gdb) PASS: gdb.base/jit-elf-so.exp: one_jit_test-1: continue to breakpoint:
break here after-dlopen
break
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/jit-elf-main.c:76^M
ERROR: GDB process no longer exists
GDB process exited with wait status 8504 exp9 0 0 CHILDKILLED SIGABRT SIGABRT
UNRESOLVED: gdb.base/jit-elf-so.exp: one_jit_test-1: setting breakpoint at
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/jit-elf-main.c:76
(eof)
...
In more detail:
...
$ gdb --args gdb -q -batch -x ./outputs/gdb.base/jit-elf-so/gdb.in.1
...
Thread 1 "gdb" received signal SIGSEGV, Segmentation fault.
0x000000000066f46c in dw2_expand_symtabs_matching_one(dwarf2_per_cu_data *,
dwarf2_per_objfile *, gdb::function_view<bool(char const*, bool)>,
gdb::function_view<bool(compunit_symtab*)>)
(per_cu=0x29b67a0, per_objfile=0x2442110, file_matcher=...,
expansion_notify=...)
at /home/vries/gdb_versions/devel/src/gdb/dwarf2/read.c:4119
4119 if (file_matcher == NULL || per_cu->v.quick->mark)
(gdb)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-05-20 19:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 19:57 vries at gcc dot gnu.org [this message]
2021-05-20 23:03 ` [Bug symtab/27893] " vries at gcc dot gnu.org
2021-05-20 23:06 ` vries at gcc dot gnu.org
2021-05-20 23:29 ` vries at gcc dot gnu.org
2021-05-21 0:14 ` vries at gcc dot gnu.org
2021-05-21 0:45 ` vries at gcc dot gnu.org
2021-05-21 1:10 ` vries at gcc dot gnu.org
2021-07-30 20:10 ` tromey at sourceware dot org
2021-08-03 23:20 ` tromey at sourceware dot org
2021-08-15 19:38 ` tromey at sourceware dot org
2021-08-24 12:13 ` vries at gcc dot gnu.org
2021-08-24 14:03 ` cvs-commit at gcc dot gnu.org
2021-08-24 14:34 ` tromey at sourceware dot org
2021-09-08 21:04 ` cvs-commit 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-27893-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).