From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id E6A923857007 for ; Wed, 1 Jul 2020 15:20:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E6A923857007 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=gnu.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=eliz@gnu.org Received: from fencepost.gnu.org ([2001:470:142:3::e]:40868) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jqeXY-00046x-30; Wed, 01 Jul 2020 11:20:48 -0400 Received: from [176.228.60.248] (port=1187 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jqeXX-0006qh-BO; Wed, 01 Jul 2020 11:20:47 -0400 Date: Wed, 01 Jul 2020 18:20:40 +0300 Message-Id: <83o8ozxnw7.fsf@gnu.org> From: Eli Zaretskii To: Simon Marchi Cc: cbiesinger@google.com, tromey@adacore.com, brobecker@adacore.com, gdb-patches@sourceware.org In-Reply-To: <56f26808-dfb0-6703-6f1f-9818c35946dd@polymtl.ca> (message from Simon Marchi on Tue, 30 Jun 2020 18:24:11 -0400) Subject: Re: Building today's snapshot of GDB with MinGW References: <83a70l20dn.fsf@gnu.org> <83wo3ozlvn.fsf@gnu.org> <56f26808-dfb0-6703-6f1f-9818c35946dd@polymtl.ca> X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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: Wed, 01 Jul 2020 15:20:50 -0000 I tried today "gdb --tui" on Windows 10, and was surprised to find that it doesn't work: the debuggee fails to start when you type "run" or "start". Windows pops up a dialog saying The application was unable to start correctly (0xc0000142) Click OK to close the application. The application whose name is shown on the popup is the debuggee, but the Windows Event Log shows a crash in the Windows console host. This is not new, I see the same problem in all versions of GDB back to 7.9. It could be related to running a 32-bit debugger on 64-bit Windows OS, though. The only discussion of this that seems relevant is here: https://github.com/msys2/MINGW-packages/issues/1744 I tried the workaround mentioned there with "set new-console on", and it didn't work. The discussion further suggests to switch the Windows console to the legacy mode, which I didn't try (because it affects all console windows and requires restart AFAICT). This URL is from 4 years ago, so maybe the current builds of Windows 10 are different; the version I tried this on is build 18362.836. Did anyone try running "gdb --tui" on Windows 10 console, and if so, did that work for you?