Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] Add sniffer for Cygwin x86_64 core dumps
Date: Sat, 22 Aug 2020 20:52:39 +0100	[thread overview]
Message-ID: <f25fc744-108c-7bf2-38ec-4ea79d9afff4@dronecode.org.uk> (raw)
In-Reply-To: <83585eda-b7ec-5735-d03e-d07ed7bcb3fe@simark.ca>

On 22/08/2020 20:41, Simon Marchi wrote:
> On 2020-08-21 12:28 p.m., Jon Turney wrote:
>> On 21/08/2020 17:22, Simon Marchi wrote:
>>> On 2020-08-21 11:25 a.m., Jon Turney wrote:
>>>> The "dumper" currently shipping in x86_64 Cygwin is utterly broken. (See [1] et seq.).
>>>>
>>>> If you use "dumper" from the latest snapshot [2], you may have more success
>>>>
>>>> [1] https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=7dd1b08836e8a7bb37d330995096540afce152a0;hp=38f88601469f4a6ab7cf42e1f076775c99eb17f2
>>>> [2] https://cygwin.com/snapshots/
>>>
>>> Ok, thanks for the tip.  I'll give it a try with a snapshot.
>>>
>>> Do I just extract cygwin-20200821.tar.xz into my current Cygwin installation to overwrite
>>> the corresponding files?  If I want to revert to the stable versions, how can I do that?
>>
>> You should be able to just extract the dumper.exe from that archive, and
>> use it.  That's what I would suggest.
> 
> Hmm, just tried that, now running "dumper" does nothing:
> 
> Baube@DESKTOP-42816MD ~
> $ dumper
> 
> Baube@DESKTOP-42816MD ~
> $ echo $?
> 127

Hmmm.  This often means the executable can't be started due to problems 
loading DLLs.

If you want to pursue this further, running under cygwin's strace (e.g. 
'strace dumper') might shed more light.

> One thing that's weird is that in my installation, binaries are in C:\cygwin64\bin,
> whereas in the snapshot, they are in usr/bin.  Did the filesystem layout change
> recently?

This is expected.

If you examine the output of 'mount', you'll see that C:\cygwin64\bin is 
mounted at /usr/bin


  reply	other threads:[~2020-08-22 19:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 19:18 [PATCH 0/4] Add gdb support for Cygwin x86_64 core dumps (v2) 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 [this message]
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
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=f25fc744-108c-7bf2-38ec-4ea79d9afff4@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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