From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 3C78C3858C20; Wed, 30 Nov 2022 09:45:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3C78C3858C20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1669801530;
	bh=mqVL2QWyV9oqu6CDY2X3/Qun4M7+EES1hp18tzjGZto=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Tn7jiPVJyrhPuhH0WUa4RwJrATAYiZixhTMUcHVpwkc10HyRCGh4/Cb6uqZ0TzPys
	 OzXcB227AJWTctpaSrRKZ31hj9uSH2rm4eivR/EzLGm5y8kEG5xiPhqASXXMKTDwqq
	 0u9EYkSfgcGN/NtHotZlVB3PNIkcDk8RPY3rxvMQ=
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: Wed, 30 Nov 2022 09:45:29 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29833-4717-togU4LRZ1C@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29833-4717@http.sourceware.org/bugzilla/>
References: <bug-29833-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29833

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(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 consu=
mes
two prompts.

So maybe this should be
...
gdb_test_no_output -no-prompt-anchor "monitor exit"
...

--=20
You are receiving this mail because:
You are on the CC list for the bug.=