From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id 1D2A13858C83 for ; Sun, 27 Mar 2022 09:55:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1D2A13858C83 Received: from [2001:470:142:3::e] (port=41364 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nYPcS-0005og-59; Sun, 27 Mar 2022 05:55:32 -0400 Received: from [87.69.77.57] (port=1963 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nYPc2-0004K5-CH; Sun, 27 Mar 2022 05:55:19 -0400 Date: Sun, 27 Mar 2022 12:55:04 +0300 Message-Id: <83ee2nafev.fsf@gnu.org> From: Eli Zaretskii To: brobecker@adacore.com CC: gdb-patches@sourceware.org In-Reply-To: <83pmm8a7gn.fsf@gnu.org> (message from Eli Zaretskii via Gdb-patches on Sat, 26 Mar 2022 21:34:32 +0300) Subject: Re: GDB 12.0.90 available for testing References: <20220320055815.2A90FA4D6C@takamaka.home> <83sfr4a93r.fsf@gnu.org> <83pmm8a7gn.fsf@gnu.org> X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2022 09:55:34 -0000 > Date: Sat, 26 Mar 2022 21:34:32 +0300 > From: Eli Zaretskii via Gdb-patches > Cc: gdb-patches@sourceware.org > > And another problem: starting this GDB under Emacs, with "M-x gdb" > (which invokes "gdb -i=mi") seems to confuse Emacs, so much so that > the debugging session is barely usable: symbols are unknown, so I > cannot set breakpoints, etc. > > There's no such problem with GDB 11.1. > > I wonder if this is a Windows specific issue. Did someone try GDB 12 > inside Emacs on GNU/Linux, and if so, did it work as expected? Turns out this is also due to the same commit that modified gdb_readline_no_editing_callback to call setbuf on all streams and any number of times, which also caused the input breakage. See PR 29002 for the details and the proposed fix.