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 54BFE3857007 for ; Thu, 2 Jul 2020 02:29:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 54BFE3857007 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]:51940) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jqoz2-00067c-EV; Wed, 01 Jul 2020 22:29:52 -0400 Received: from [176.228.60.248] (port=3597 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jqoyz-00078j-MM; Wed, 01 Jul 2020 22:29:50 -0400 Date: Thu, 02 Jul 2020 05:29:46 +0300 Message-Id: <83ftaay7hh.fsf@gnu.org> From: Eli Zaretskii To: Christian Biesinger Cc: simon.marchi@polymtl.ca, tromey@adacore.com, brobecker@adacore.com, gdb-patches@sourceware.org In-Reply-To: (message from Christian Biesinger on Wed, 1 Jul 2020 14:25:22 -0500) 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> <83o8ozxnw7.fsf@gnu.org> 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: Thu, 02 Jul 2020 02:29:56 -0000 > From: Christian Biesinger > Date: Wed, 1 Jul 2020 14:25:22 -0500 > Cc: Simon Marchi , Tom Tromey , > Joel Brobecker , gdb-patches > > > The application was unable to start correctly (0xc0000142) > > Click OK to close the application. > > Odd... that's STATUS_DLL_INIT_FAILED... Right. > I see the same thing, with mingw64. And after that, the cmd.exe window > seems to hang for some seconds and then the entire window closes > (crashes, presumably, but no crash dialog). No crash dialog, but you will see in the Windows Event Log that the console host crashed. > I don't have time right now to look into this any further, but I can > confirm you're not the only one. Thanks for verifying that.