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 39F393844014 for ; Tue, 18 Aug 2020 16:15:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 39F393844014 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]:54999) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k84HB-000272-Lk; Tue, 18 Aug 2020 12:15:53 -0400 Received: from [176.228.60.248] (port=2435 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1k84HB-0002C7-68; Tue, 18 Aug 2020 12:15:53 -0400 Date: Tue, 18 Aug 2020 19:15:40 +0300 Message-Id: <83zh6sdj6b.fsf@gnu.org> From: Eli Zaretskii To: Jon Turney Cc: gdb-patches@sourceware.org In-Reply-To: <5ef259bf-f3cd-d22f-883b-25ba550adbd9@dronecode.org.uk> (message from Jon Turney on Tue, 18 Aug 2020 16:32:45 +0100) Subject: Re: [PATCH 0/4] Add gdb support for Cygwin x86_64 core dumps (v2) References: <20200812191816.23246-1-jon.turney@dronecode.org.uk> <83v9hnmzl2.fsf@gnu.org> <80a890c4-e86a-5f19-e5d7-b1ff91c57ea3@dronecode.org.uk> <831rkamr0d.fsf@gnu.org> <5ef259bf-f3cd-d22f-883b-25ba550adbd9@dronecode.org.uk> X-Spam-Status: No, score=-4.0 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: Tue, 18 Aug 2020 16:15:56 -0000 > Cc: Eli Zaretskii > From: Jon Turney > Date: Tue, 18 Aug 2020 16:32:45 +0100 > > I'll make a patch to add "GDB now supports core file debugging for > x86_64 Cygwin programs." to NEWS. Thanks, that'll be good, I think. > > Is there perhaps something special that needs to be done to produce > > Cygwin core files? Or do you use the same commands as on Posix hosts > > ("ulimit -c" etc.)? > There are some special steps needed at the moment (more due to > implementation shortcomings than real difficulties), which are described > in Cygwin documentation. > > I can't find any mention of 'ulimit -c' or how core files might be > produced on any platform in the current gdb documentation, so I'm not > sure why Cygwin needs to be a special case here. Then I guess NEWS should be enough. Thanks.