Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Add gdb support for Cygwin x86_64 core dumps (v2)
Date: Tue, 18 Aug 2020 16:32:45 +0100	[thread overview]
Message-ID: <5ef259bf-f3cd-d22f-883b-25ba550adbd9@dronecode.org.uk> (raw)
In-Reply-To: <831rkamr0d.fsf@gnu.org>

On 13/08/2020 17:48, Eli Zaretskii wrote:
>> Cc: Eli Zaretskii <eliz@gnu.org>
>> From: Jon Turney <jon.turney@dronecode.org.uk>
>> 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.


  reply	other threads:[~2020-08-18 15:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 19:18 Jon Turney
2020-08-12 19:18 ` [PATCH 1/4] Add sniffer for Cygwin x86_64 core dumps Jon Turney
2020-08-20 22:20   ` Simon Marchi
2020-08-21 15:25     ` Jon Turney
2020-08-21 16:22       ` Simon Marchi
2020-08-21 16:28         ` Jon Turney
2020-08-22 19:41           ` Simon Marchi
2020-08-22 19:52             ` Jon Turney
2020-08-24 15:47               ` Simon Marchi
2020-08-24 17:02                 ` Jon Turney
2020-08-12 19:18 ` [PATCH 2/4] Add amd64_windows_gregset_reg_offset Jon Turney
2020-08-20 22:08   ` Simon Marchi
2020-09-18 16:31     ` Jon Turney
2020-08-12 19:18 ` [PATCH 3/4] Promote windows_core_xfer_shared_libraries and windows_core_pid_to_str Jon Turney
2020-08-12 19:18 ` [PATCH 4/4] Add handling for 64-bit module addresses in Cygwin core dumps Jon Turney
2020-08-24 18:34   ` Simon Marchi
2020-09-15 21:44     ` Jon Turney
2020-09-16  2:20       ` Simon Marchi
2020-09-16  9:15         ` Christian Biesinger
2020-08-12 19:30 ` [PATCH 0/4] Add gdb support for Cygwin x86_64 core dumps (v2) Eli Zaretskii
2020-08-13 14:43   ` Jon Turney
2020-08-13 16:48     ` Eli Zaretskii
2020-08-18 15:32       ` Jon Turney [this message]
2020-08-18 16:15         ` Eli Zaretskii

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=5ef259bf-f3cd-d22f-883b-25ba550adbd9@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=gdb-patches@sourceware.org \
    /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