From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-044.btinternet.com (mailomta23-re.btinternet.com [213.120.69.116]) by sourceware.org (Postfix) with ESMTPS id B07263857C4D for ; Tue, 18 Aug 2020 15:32:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B07263857C4D Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=jon.turney@dronecode.org.uk Received: from re-prd-rgout-001.btmx-prd.synchronoss.net ([10.2.54.4]) by re-prd-fep-044.btinternet.com with ESMTP id <20200818153245.CAND21348.re-prd-fep-044.btinternet.com@re-prd-rgout-001.btmx-prd.synchronoss.net>; Tue, 18 Aug 2020 16:32:45 +0100 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com X-Originating-IP: [86.141.130.84] X-OWM-Source-IP: 86.141.130.84 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgeduiedruddtiedgjeefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefuvfhfhffkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpeeguefhkedvfeeigefhhedtjeehieegtdehhffhheffgfehheegtdffleejteeuueenucfkphepkeeirddugedurddufedtrdekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddrudduudgnpdhinhgvthepkeeirddugedurddufedtrdekgedpmhgrihhlfhhrohhmpeeojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhequceuqfffjgepkeeukffvoffkoffgpdhrtghpthhtohepoegvlhhiiiesghhnuhdrohhrgheqpdhrtghpthhtohepoehguggsqdhprghttghhvghssehsohhurhgtvgifrghrvgdrohhrgheq X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.111] (86.141.130.84) by re-prd-rgout-001.btmx-prd.synchronoss.net (5.8.340) (authenticated as jonturney@btinternet.com) id 5ED9BDD00C6659C8; Tue, 18 Aug 2020 16:32:45 +0100 Subject: Re: [PATCH 0/4] Add gdb support for Cygwin x86_64 core dumps (v2) To: gdb-patches@sourceware.org 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> From: Jon Turney Message-ID: <5ef259bf-f3cd-d22f-883b-25ba550adbd9@dronecode.org.uk> Date: Tue, 18 Aug 2020 16:32:45 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <831rkamr0d.fsf@gnu.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_NONE, 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 15:32:48 -0000 On 13/08/2020 17:48, Eli Zaretskii wrote: >> Cc: Eli Zaretskii >> From: Jon Turney >> Date: Thu, 13 Aug 2020 15:43:41 +0100 >> >>> Thanks, but isn't this NEWS-worthy? >> >> This doesn't add a new feature to gdb, just (belatedly) makes it work on >> x86_64 Cygwin as it does on x86 cygwin. >> >> What would you suggest adding to NEWS? > > Something like "GDB now supports core file debugging for Cygwin > programs." This feature has existed for x86 Cygwin since 2000 (and it's been possible to try to use it for x86_64 since that was added, but it just fails with an assert) I'll make a patch to add "GDB now supports core file debugging for x86_64 Cygwin programs." to NEWS. >> > And what about some documentation >> > for the manual? >> >> No changes should be needed to the existing documentation of debugging >> using core files (since there shouldn't be any difference in behaviour >> when using Cygwin core dumps) > > 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.