public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-29002-4717-xfpEL2iSvU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29002-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29002
--- 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.
>
> To reproduce the issue, I have the following scenario in PowerShell:
>
> $ cat input
> 1-list-thread-groups
> 2-list-thread-groups
> 3-list-thread-groups
>
> cat input | arm-none-eabi-gdb.exe --silent --interpreter=mi2
> =thread-group-added,id="i1"
> (gdb)
> 1^done,groups=[{id="i1",type="process"}]
> (gdb)
> &"warning: Exception condition detected on fd 0\n"
> &"error detected on stdin\n"
>
>
>
> 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.
For the same input, but using the native MS-Windows GDB, I get this:
d:\usr>cat gdb.input | gdb --silent --interpreter=mi2
=thread-group-added,id="i1"
(gdb)
1^done,groups=[{id="i1",type="process"}]
(gdb)
2^done,groups=[{id="i1",type="process"}]
(gdb)
3^done,groups=[{id="i1",type="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 PowerShell.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-11 15:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 5:33 [Bug mi/29002] New: " eliz at gnu dot org
2022-03-27 5:35 ` [Bug mi/29002] " eliz at gnu dot org
2022-03-27 6:20 ` eliz at gnu dot org
2022-03-27 6:23 ` eliz at gnu dot org
2022-03-27 9:48 ` eliz at gnu dot org
2022-03-27 9:52 ` eliz at gnu dot org
2022-04-24 15:43 ` cvs-commit at gcc dot gnu.org
2022-04-24 15:44 ` cvs-commit at gcc dot gnu.org
2022-04-24 15:46 ` brobecker at gnat dot com
2023-07-11 13:01 ` equationssolver at yahoo dot com
2023-07-11 13:11 ` equationssolver at yahoo dot com
2023-07-11 15:38 ` eliz at gnu dot org [this message]
2023-07-13 14:05 ` equationssolver at yahoo dot com
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-29002-4717-xfpEL2iSvU@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).