public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31435] [gdb/testsuite] Runtest error running DAP tests
Date: Fri, 15 Mar 2024 13:39:13 +0000 [thread overview]
Message-ID: <bug-31435-4717-QjOrK44JK4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31435-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31435
--- Comment #9 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Tom Tromey from comment #8)
> Both these spots use "wait -nowait" but I wonder if it's just
> better to use remote_wait with a timeout instead.
Oh, never mind, remote_wait is written to only handle
a single spawnee. dejagnu :(
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-15 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 12:58 [Bug testsuite/31435] New: " vries at gcc dot gnu.org
2024-02-29 13:19 ` [Bug testsuite/31435] " vries at gcc dot gnu.org
2024-02-29 15:52 ` tromey at sourceware dot org
2024-03-14 16:37 ` tromey at sourceware dot org
2024-03-14 17:29 ` tromey at sourceware dot org
2024-03-14 17:57 ` tromey at sourceware dot org
2024-03-14 20:13 ` vries at gcc dot gnu.org
2024-03-15 9:15 ` vries at gcc dot gnu.org
2024-03-15 13:33 ` tromey at sourceware dot org
2024-03-15 13:38 ` tromey at sourceware dot org
2024-03-15 13:39 ` tromey at sourceware dot org [this message]
2024-03-15 14:30 ` tromey at sourceware dot org
2024-03-18 13:01 ` cvs-commit at gcc dot gnu.org
2024-03-18 13:02 ` tromey at sourceware dot 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-31435-4717-QjOrK44JK4@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).