public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: cygwin Rsync x32 issue
Date: Sun, 14 Feb 2021 21:21:55 -0500	[thread overview]
Message-ID: <dda0c248-643b-ed5f-6194-0cd322bce316@cornell.edu> (raw)
In-Reply-To: <8f0ae573-df06-0fed-3e39-a0f56fb6f1a9@jbrain.com>

On 2/14/2021 9:04 PM, Jim Brain wrote:
> On 2/14/2021 6:01 PM, Ken Brown via Cygwin wrote:
>> On 2/13/2021 11:33 PM, Jim Brain wrote:
>>>
>>
>> There was a bug in Cygwin's implementation of fstatat(2) that was recently 
>> reported and fixed.  It affected 32-bit only.  On the chance that you've 
>> bumped into the same bug, you could try a snapshot of cygwin1.dll to see if 
>> that fixes the problem:
>>
>>   https://cygwin.com/snapshots/
> 
> Thanks for the idea.  I dloaded the new DLL, but no joy.  Same error.

OK, it was a long shot.

Please run the failing rsync command under strace, like this:

   strace -o rsync.strace rsync...

Then post rsync.strace somewhere where people can look at it.

Ken

  reply	other threads:[~2021-02-15  2:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14  4:33 Jim Brain
2021-02-14  5:39 ` Brian Inglis
2021-02-14  5:55   ` Jim Brain
2021-02-15  0:01 ` Ken Brown
2021-02-15  2:04   ` Jim Brain
2021-02-15  2:21     ` Ken Brown [this message]
2021-02-15  2:48       ` Jim Brain
2021-02-15 23:18         ` Ken Brown
2021-02-16  1:57           ` Jim Brain
2021-02-16  2:11             ` Jim Brain
2021-02-16 12:30           ` Ken Brown
2021-02-16 23:32             ` Jim Brain
2021-02-18  6:35       ` Andrey Repin
2021-02-18 21:50         ` Ken Brown
  -- strict thread matches above, loose matches on Subject: below --
2020-12-13 22:49 Jim Brain

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=dda0c248-643b-ed5f-6194-0cd322bce316@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).