public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Jon Turney <jon.turney@dronecode.org.uk>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: gdb and core files
Date: Mon, 29 Jun 2020 12:03:10 -0400	[thread overview]
Message-ID: <2a11eebe-d516-fb0a-e340-9619dc3b608f@cornell.edu> (raw)
In-Reply-To: <0acaf9fc-a490-78d3-9328-64e97d7eeb79@dronecode.org.uk>

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.

Ken

  reply	other threads:[~2020-06-29 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28  0:50 Ken Brown
2020-06-28 13:31 ` Jon Turney
2020-06-29 16:03   ` Ken Brown [this message]
2020-06-30  3:24     ` Mark Geisert
2020-07-01 21:37       ` Jon Turney
2020-07-03  6:37         ` Mark Geisert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2a11eebe-d516-fb0a-e340-9619dc3b608f@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).