From: Mark Geisert <mark@maxrnd.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: gdb and core files
Date: Thu, 2 Jul 2020 23:37:40 -0700 [thread overview]
Message-ID: <97dc2160-ea87-d9ff-40e9-083933800d44@maxrnd.com> (raw)
In-Reply-To: <6595e2f2-0578-515a-a164-a10d692981cf@dronecode.org.uk>
Jon Turney wrote:
> On 30/06/2020 04:24, Mark Geisert wrote:
>> 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
>
> Yeah, with hindsight, that would have been a good idea.
>
>> 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.
>
> I had a poke at this problem this week.
>
> [1] https://cygwin.com/pipermail/cygwin-patches/2020q3/010313.html
> [2] https://sourceware.org/pipermail/gdb-patches/2020-July/170023.html
Ow, I've been ninja'd! Seriously, nice to see this work. Great!
>> 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.
>
> Not quite. There's already a tool ('minidumper') to generate minidumps. But
> gdb can't read those (yet).
Appreciate the correction. I'll check in when I can spend time on this.
Cheers,
..mark
prev parent reply other threads:[~2020-07-03 6:37 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
2020-06-30 3:24 ` Mark Geisert
2020-07-01 21:37 ` Jon Turney
2020-07-03 6:37 ` Mark Geisert [this message]
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=97dc2160-ea87-d9ff-40e9-083933800d44@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@cygwin.com \
/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).