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 381813858D20; Tue, 11 Jul 2023 15:38:18 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 381813858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1689089898;
	bh=COd9AvT0Aal7QrgjgPmHwIG/678J3D8qTIwLjG4iHwc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=vwUXjuw1/O3fTw899c7rXDhBJWEZjW+4qM8PC9FRb3OZX3p5hWw+FqoMyWUQ3VHuf
	 1rKytu4XX5zbZobGaXE06k3O4F5CdT5TszQmnAMgPw4QPqnxOiIKdaNMkH/ALshvGo
	 BmdFevIkL7KR69LZsv2VCXp4LBUwHuWm/QJUoUYA=
From: "eliz at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/29002] Console input broken in MI mode
Date: Tue, 11 Jul 2023 15:38:18 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: mi
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eliz at gnu dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: aburgess at redhat dot com
X-Bugzilla-Target-Milestone: 12.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29002-4717-xfpEL2iSvU@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29002-4717@http.sourceware.org/bugzilla/>
References: <bug-29002-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=3D29002

--- Comment #10 from Eli Zaretskii <eliz at gnu dot org> ---
(In reply to hmb from comment #8)
> I'm still encountering an error with the latest 13.2 release of GDB on a
> Windows host. When using GDB, I'm not receiving responses for the MI
> commands, causing my IDE (Eclipse) to freeze and become unresponsive.
>=20
> To reproduce the issue, I have the following scenario in PowerShell:
>=20
> $  cat input
> 1-list-thread-groups
> 2-list-thread-groups
> 3-list-thread-groups
>=20
> cat input | arm-none-eabi-gdb.exe --silent --interpreter=3Dmi2
> =3Dthread-group-added,id=3D"i1"
> (gdb)
> 1^done,groups=3D[{id=3D"i1",type=3D"process"}]
> (gdb)
> &"warning: Exception condition detected on fd 0\n"
> &"error detected on stdin\n"
>=20
>=20
>=20
> As observed, there is no response for the MI commands numbered 2 and 3."

I cannot reproduce this with GDB 13.1 I built myself with mingw.org's MinGW=
.=20
For the same input, but using the native MS-Windows GDB, I get this:

d:\usr>cat gdb.input | gdb  --silent --interpreter=3Dmi2
=3Dthread-group-added,id=3D"i1"
(gdb)
1^done,groups=3D[{id=3D"i1",type=3D"process"}]
(gdb)
2^done,groups=3D[{id=3D"i1",type=3D"process"}]
(gdb)
3^done,groups=3D[{id=3D"i1",type=3D"process"}]
(gdb)
&"warning: Exception condition detected on fd 0\n"
&"error detected on stdin\n"

So all the 3 commands were processed.

In case it's important, I ran this command from cmd.exe, not from PowerShel=
l.

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