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: Sun, 27 Mar 2022 06:23:51 +0000	[thread overview]
Message-ID: <bug-29002-4717-YnL2QeXec1@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 #2 from Eli Zaretskii <eliz at gnu dot org> ---
The culprit is this commit:

  commit d08cbc5d3203118da5583296e49273cf82378042
  Author:     Andrew Burgess <aburgess@redhat.com>
  AuthorDate: Wed Dec 22 12:57:44 2021 +0000
  Commit:     Andrew Burgess <aburgess@redhat.com>
  CommitDate: Mon Feb 7 10:24:27 2022 +0000

      gdb: unbuffer all input streams when not using readline

I guess the detailed analysis in that commit, which describes the behavior of
glibc and the Linux kernel, doesn't fully apply to MS-Windows and its C
runtime...

The patch I proposed, which partially reverts that commit, fixes the issue for
me on MS-Windows.  But if we want to keep the current code for GNU/Linux and
other platforms, I guess the actual fix will need to be more complex.

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

  parent reply	other threads:[~2022-03-27  6:23 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 [this message]
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
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-YnL2QeXec1@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).