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 testsuite/29734] New: [gdb/testsuite, local-remote-host-native] FAIL: gdb.server/stop-reply-no-thread-multi.exp: target-non-stop=off: to_disable=: set remote threads-packet off (timeout)
Date: Mon, 31 Oct 2022 08:46:47 +0000 [thread overview]
Message-ID: <bug-29734-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29734
Bug ID: 29734
Summary: [gdb/testsuite, local-remote-host-native] FAIL:
gdb.server/stop-reply-no-thread-multi.exp:
target-non-stop=off: to_disable=: set remote
threads-packet off (timeout)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
I tried out running the gdb.server/*.exp test-cases with host+target board
local-remote-host-native, but in the first test-case run into a time-out:
...
(gdb) PASS: gdb.server/stop-reply-no-thread-multi.exp: target-non-stop=off:
to_disable=: disconnect
builtin_spawn /usr/bin/ssh -t -l vries 127.0.0.1
/home/vries/gdb_versions/devel/build/gdb/testsuite/../../gdbserver/gdbserver
--once localhost:2346
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/stop-reply-no-thread-multi/stop-reply-no-thread-multi^M
Process
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/stop-reply-no-thread-multi/stop-reply-no-thread-multi
created; pid = 32600^M
Listening on port 2346^M
set remote threads-packet off^M
FAIL: gdb.server/stop-reply-no-thread-multi.exp: target-non-stop=off:
to_disable=: set remote threads-packet off (timeout)
...
AFAICT, this is due to this line in ${board}_spawn:
...
set board_info($board,fileid) $spawn_id
...
We have the following series of events:
- gdb is spawned, setting fileid
- a few gdb commands (set height etc) are send using fileid, and are successful
- gdbserver is spawned, overwriting fileid
- the next gdb command is sent to gdb using fileid, so it's send
to gdbserver instead of gdb, and we run into the timeout.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-31 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 8:46 vries at gcc dot gnu.org [this message]
2023-03-28 15:48 ` [Bug testsuite/29734] " cvs-commit at gcc dot gnu.org
2023-03-28 15:51 ` 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-29734-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).