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/29833] [gdb] FAIL: gdb.server/monitor-exit-quit.exp: monitor exit
Date: Mon, 15 Jan 2024 09:20:27 +0000 [thread overview]
Message-ID: <bug-29833-4717-ZUfDvnIAeO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29833-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29833
--- Comment #14 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> (In reply to Tom de Vries from comment #0)
> > I ran into:
> > ...
> > (gdb) monitor exit^M
> > (gdb) Remote connection closed^M
> > (gdb) FAIL: gdb.server/monitor-exit-quit.exp: monitor exit
> > ...
>
> It's interesting though, we have:
> ...
> gdb_test_no_output "monitor exit"
> ...
> so given the point where the FAIL is produced, the gdb_test_no_output
> consumes two prompts.
>
> So maybe this should be
> ...
> gdb_test_no_output -no-prompt-anchor "monitor exit"
> ...
And on that note, with read1 we have:
...
(gdb) monitor exit^M
(gdb) PASS: gdb.server/monitor-exit-quit.exp: monitor exit
Remote connection closed^M
(gdb) FAIL: gdb.server/monitor-exit-quit.exp: set confirm off
set confirm off^M
(gdb) FAIL: gdb.server/monitor-exit-quit.exp: quit (prompt)
qupoitrt^M
2mo41ni1^Mto
Rr emexotite ^M
debugging from host ::1, port 45844^M
Killing process(es): 28565^M
testcase /data/vries/gdb/src/gdb/testsuite/gdb.server/monitor-exit-quit.exp
completed in 1 seconds
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-15 9:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 7:19 [Bug gdb/29833] New: " vries at gcc dot gnu.org
2022-11-30 8:11 ` [Bug gdb/29833] " vries at gcc dot gnu.org
2022-11-30 9:45 ` vries at gcc dot gnu.org
2022-11-30 12:50 ` simark at simark dot ca
2022-12-01 9:50 ` vries at gcc dot gnu.org
2022-12-01 10:59 ` vries at gcc dot gnu.org
2022-12-01 11:18 ` vries at gcc dot gnu.org
2023-01-06 18:05 ` vries at gcc dot gnu.org
2023-01-07 17:42 ` vries at gcc dot gnu.org
2023-01-09 14:53 ` vries at gcc dot gnu.org
2023-01-09 14:53 ` vries at gcc dot gnu.org
2023-01-10 10:43 ` vries at gcc dot gnu.org
2023-01-10 14:00 ` vries at gcc dot gnu.org
2023-03-11 15:03 ` vries at gcc dot gnu.org
2024-01-15 9:20 ` vries at gcc dot gnu.org [this message]
2024-01-16 7:35 ` [Bug testsuite/29833] " 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-29833-4717-ZUfDvnIAeO@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).