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 6F3B0385841D; Mon, 15 Jan 2024 09:20:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6F3B0385841D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1705310428;
	bh=VNI7uCEsDxIvczmqI8Fl9QrvRbAFkyj7XOzqjUZ6L3A=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=KXLvepgl5703et3la1R57TVxsvgCH+eCxyUwZL0gVw8E6wIoCzRUVCh777hvJbjWd
	 7hNnx+077IzZxTMI2kZTCEw/AEqE4vXGvLsvy80Mz5184lYOzb0yCcs/GIrCX1/dRA
	 sxPpG/aqmapawU14E9WzhpaltUdU1E/s+cZygiFo=
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
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-ZUfDvnIAeO@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 #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
> > ...
>=20
> 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.
>=20
> 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
...

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