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 server/30222] New: [gdb/server] wait_1: Assertion `step_over_bkpt == null_ptid' failed
Date: Sat, 11 Mar 2023 11:49:48 +0000 [thread overview]
Message-ID: <bug-30222-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30222
Bug ID: 30222
Summary: [gdb/server] wait_1: Assertion `step_over_bkpt ==
null_ptid' failed
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: server
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
For test-case gdb.threads/step-over-exec, target board native-gdbserver I
spotted a gdbserver assertion failure:
...
Exec-ing
/data/vries/gdb/leap-15-4/build/gdb/testsuite/outputs/gdb.threads/step-over-exec/step-over-exec-execr-thread-leader-diff-text-segs-true-execd^M
/data/vries/gdb/src/gdbserver/linux-low.cc:3585: A problem internal to
GDBserver has been detected.^M
wait_1: Assertion `step_over_bkpt == null_ptid' failed.^M
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-03-11 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 11:49 vries at gcc dot gnu.org [this message]
2023-03-28 20:22 ` [Bug server/30222] " 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-30222-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).