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 gdb/30547] New: [gdb, s390x] segfault in for_each_block
Date: Tue, 13 Jun 2023 13:16:28 +0000 [thread overview]
Message-ID: <bug-30547-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30547
Bug ID: 30547
Summary: [gdb, s390x] segfault in for_each_block
Product: gdb
Version: 13.1
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With a gdb 13.2 based package on s390x SLE-15, I run into:
...
(gdb) PASS: gdb.base/vfork-follow-parent.exp:
resolution_method=schedule-multiple: print unblock_parent = 1
continue^M
Continuing.^M
Reading symbols from
/home/abuild/rpmbuild/BUILD/gdb-13.2/build-s390x-suse-linux/gdb/testsuite.unix.-m64.-fno-PIE.-no-pie/outputs/gdb.base/vfork-follow-parent/vfork-follow-parent...^M
^M
^M
Fatal signal: Segmentation fault^M
----- Backtrace -----^M
0x2aa323927c1 gdb_internal_backtrace_1^M
../../gdb/bt-utils.c:122^M
0x2aa323927c1 _Z22gdb_internal_backtracev^M
../../gdb/bt-utils.c:168^M
0x2aa324cbb37 handle_fatal_signal^M
../../gdb/event-top.c:971^M
0x2aa324cbc13 handle_sigsegv^M
../../gdb/event-top.c:1044^M
0x3ffcc2fd74d ???^M
0x2aa32430ad0 for_each_block^M
../../gdb/dcache.c:199^M
0x2aa32430ad0 _Z17dcache_invalidateP13dcache_struct^M
../../gdb/dcache.c:251^M
0x2aa3256f019 _Z20fetch_inferior_eventv^M
../../gdb/infrun.c:4162^M
0x2aa32a23049 gdb_wait_for_event^M
../../gdbsupport/event-loop.cc:694^M
0x2aa32a239e1 _Z16gdb_do_one_eventi^M
../../gdbsupport/event-loop.cc:217^M
0x2aa325c0605 start_event_loop^M
../../gdb/main.c:411^M
0x2aa325c0605 captured_command_loop^M
../../gdb/main.c:471^M
0x2aa325c20b7 captured_main^M
../../gdb/main.c:1330^M
0x2aa325c20b7 _Z8gdb_mainP18captured_main_args^M
../../gdb/main.c:1345^M
0x2aa32293945 main^M
../../gdb/gdb.c:32^M
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-06-13 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 13:16 vries at gcc dot gnu.org [this message]
2023-10-31 8:02 ` [Bug gdb/30547] [gdb, s390x, ppc64] " vries at gcc dot gnu.org
2023-10-31 8:28 ` vries at gcc dot gnu.org
2023-10-31 15:53 ` vries at gcc dot gnu.org
2023-11-01 9:42 ` vries at gcc dot gnu.org
2023-11-01 9:56 ` vries at gcc dot gnu.org
2023-11-02 10:49 ` vries at gcc dot gnu.org
2023-11-04 15:57 ` vries at gcc dot gnu.org
2023-11-28 9:31 ` cvs-commit at gcc dot gnu.org
2023-11-28 9:31 ` cvs-commit at gcc dot gnu.org
2023-11-28 9:54 ` 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-30547-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).