X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7BE893858D37 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=mark AT maxrnd DOT com Subject: Re: gdb and core files To: The Cygwin Mailing List References: <7e6b53dd-ef3d-e451-86f9-1a2c3d12209e AT cornell DOT edu> <0acaf9fc-a490-78d3-9328-64e97d7eeb79 AT dronecode DOT org DOT uk> <2a11eebe-d516-fb0a-e340-9619dc3b608f AT cornell DOT edu> From: Mark Geisert Message-ID: Date: Mon, 29 Jun 2020 20:24:52 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <2a11eebe-d516-fb0a-e340-9619dc3b608f@cornell.edu> X-Spam-Status: No, score=-7.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252"; Format="flowed" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 05U3Pbpp019427 Ken Brown via Cygwin wrote: > On 6/28/2020 9:31 AM, Jon Turney wrote: >> On 28/06/2020 01:50, Ken Brown via Cygwin wrote: >>> Following the instructions at >>> https://cygwin.com/cygwin-ug-net/using-cygwinenv.html, I tried to create a >>> core file that I could examine with gdb, but I apparently ran into a gdb bug. >>> I tried both gdb 9.2-1 and 8.3.1-1.  Here are the results with 9.2-1. >>> >> [...] >> >> Unfortunately, I think dumper doesn't produce anything useful on x86_64. See >> [1] et seq. > > Thanks.  Sorry I didn't notice that people had asked the same question before. > > We should probably fix the documentation: > >   https://cygwin.com/cygwin-ug-net/using-cygwinenv.html >   https://cygwin.com/cygwin-ug-net/dumper.html > > Or maybe we should just remove all mention of dumper from the documentation. > Given that we're trying to move people away from 32-bit Cygwin, I don't think it > makes sense to document a feature that works only on the latter. I hesitate to comment when I can't immediately work on this, but, ...making dumper work on 64-bit Cygwin is on my TODO list but not right at the top. It would be helpful to keep the program around in its current 32-bit state as a template for 64-bit. Re the documentation, I do think the first example should probably not mention dumper, or should parenthetically add "(32-bit only)". The second example doc should say somewhere that the tool is currently 32-bit only. In addition, the current dumper should probably detect when it's running in the wrong environment and stop with an error, rather than running as if it's doing something useful. Whatever is decided for the short term, I can make time to implement that. ..mark P.S. For the long term, I think it was Jon who suggested dumper generate Windows minidumps rather than the current Frankensteinish dumps. I intend to investigate that when I get to this project. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple