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] [gdb, s390x, ppc64] segfault in for_each_block
Date: Tue, 31 Oct 2023 08:02:13 +0000 [thread overview]
Message-ID: <bug-30547-4717-Fov87WwSKE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30547-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30547
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[gdb, s390x] segfault in |[gdb, s390x, ppc64]
|for_each_block |segfault in for_each_block
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Also ran into this with gdb-14-branch and centos-7 ppc64:
...
PASS: gdb.base/vfork-follow-parent.exp: exec_file=vfork-follow-parent-exit:
target-non-stop=on: non-stop=off: resolution_method=schedule-multiple: print
unblock_parent = 1
ERROR: GDB process no longer exists
UNRESOLVED: gdb.base/vfork-follow-parent.exp:
exec_file=vfork-follow-parent-exit: target-non-stop=on: non-stop=off:
resolution_method=schedule-multiple: continue to break_parent
...
PASS: gdb.base/vfork-follow-parent.exp: exec_file=vfork-follow-parent-exit:
target-non-stop=off: non-stop=off: resolution_method=schedule-multiple: print
unblock_parent = 1
ERROR: GDB process no longer exists
UNRESOLVED: gdb.base/vfork-follow-parent.exp:
exec_file=vfork-follow-parent-exit: target-non-stop=off: non-stop=off:
resolution_method=schedule-multiple: continue to break_parent
...
In more detail:
...
(gdb) PASS: gdb.base/vfork-follow-parent.exp:
exec_file=vfork-follow-parent-exit: target-non-stop=on: non-stop=off:
resolution_method=schedule-multiple: print unblock_parent = 1
continue
Continuing.
Reading symbols from
/home/vries/gdb/build/gdb/testsuite/outputs/gdb.base/vfork-follow-parent/vfork-follow-parent-exit...
Fatal signal: Segmentation fault
----- Backtrace -----
0x1027d3e7 gdb_internal_backtrace_1
/home/vries/gdb/src/gdb/bt-utils.c:122
0x1027d54f _Z22gdb_internal_backtracev
/home/vries/gdb/src/gdb/bt-utils.c:168
0x1057643f handle_fatal_signal
/home/vries/gdb/src/gdb/event-top.c:889
0x10576677 handle_sigsegv
/home/vries/gdb/src/gdb/event-top.c:962
0x3fffad660477 ???
0x103f2144 for_each_block
/home/vries/gdb/src/gdb/dcache.c:199
0x103f235b _Z17dcache_invalidateP13dcache_struct
/home/vries/gdb/src/gdb/dcache.c:251
0x10bde8c7 _Z24target_dcache_invalidatev
/home/vries/gdb/src/gdb/target-dcache.c:50
0x106a4f27 _Z20fetch_inferior_eventv
/home/vries/gdb/src/gdb/infrun.c:4420
0x10670d63 _Z22inferior_event_handler19inferior_event_type
/home/vries/gdb/src/gdb/inf-loop.c:42
0x1071a0c7 handle_target_event
/home/vries/gdb/src/gdb/linux-nat.c:4243
0x1176159f handle_file_event
/home/vries/gdb/src/gdbsupport/event-loop.cc:573
0x11761b77 gdb_wait_for_event
/home/vries/gdb/src/gdbsupport/event-loop.cc:694
0x1176019f _Z16gdb_do_one_eventi
/home/vries/gdb/src/gdbsupport/event-loop.cc:217
0x1078a3bf start_event_loop
/home/vries/gdb/src/gdb/main.c:407
0x1078a647 captured_command_loop
/home/vries/gdb/src/gdb/main.c:471
0x1078caff captured_main
/home/vries/gdb/src/gdb/main.c:1324
0x1078cbf3 _Z8gdb_mainP18captured_main_args
/home/vries/gdb/src/gdb/main.c:1343
0x10019b9f main
/home/vries/gdb/src/gdb/gdb.c:39
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
ERROR: GDB process no longer exists
GDB process exited with wait status 56538 exp20 0 0 CHILDKILLED SIGSEGV
{segmentation violation}
UNRESOLVED: gdb.base/vfork-follow-parent.exp:
exec_file=vfork-follow-parent-exit: target-non-stop=on: non-stop=off:
resolution_method=schedule-multiple: continue to break_parent
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-31 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 13:16 [Bug gdb/30547] New: [gdb, s390x] " vries at gcc dot gnu.org
2023-10-31 8:02 ` vries at gcc dot gnu.org [this message]
2023-10-31 8:28 ` [Bug gdb/30547] [gdb, s390x, ppc64] " 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-Fov87WwSKE@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).