public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/29002] Console input broken in MI mode Date: Sun, 24 Apr 2022 15:43:10 +0000 [thread overview] Message-ID: <bug-29002-4717-KTIeSwf0eI@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 #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Joel Brobecker <brobecke@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ac16b09d7e5fd0013ffa27e4d0531c0af12a529a commit ac16b09d7e5fd0013ffa27e4d0531c0af12a529a Author: Andrew Burgess <aburgess@redhat.com> Date: Sun Apr 24 08:39:19 2022 -0700 gdb: move setbuf calls out of gdb_readline_no_editing_callback After this commit: commit d08cbc5d3203118da5583296e49273cf82378042 Date: Wed Dec 22 12:57:44 2021 +0000 gdb: unbuffer all input streams when not using readline Issues were reported with some MS-Windows hosts, see the thread starting here: https://sourceware.org/pipermail/gdb-patches/2022-March/187004.html Filed in bugzilla as: PR mi/29002 The problem seems to be that calling setbuf on terminal file handles is not always acceptable, see this mail for more details: https://sourceware.org/pipermail/gdb-patches/2022-April/187310.html This commit does two things, first moving the setbuf calls out of gdb_readline_no_editing_callback so that we don't end up calling setbuf so often. Then, for MS-Windows hosts, we don't call setbuf for terminals, this appears to resolve the issues that have been reported. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29002 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-24 15:43 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 [this message] 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-KTIeSwf0eI@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: linkBe 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).