Re: cygwin Rsync x32 issue

[Jim Brain <brain@jbrain.com>]

On 2/15/2021 5:18 PM, Ken Brown via Cygwin wrote:
> On 2/14/2021 9:48 PM, Jim Brain wrote:
>> On 2/14/2021 8:21 PM, Ken Brown via Cygwin wrote:
>>>
>>>
>>>   strace -o rsync.strace rsync...
>>>
>>> Then post rsync.strace somewhere where people can look at it.
>>
>> https://www.dropbox.com/s/v1n9i77jhq3b3zh/rsync.strace?dl=0
>
> Thanks.  For the sake of comparison, could you also post the strace 
> output from a successful (64-bit) run?  I saw a suspicious 
> CreateProcess failure, but I'd like to be sure it doesn't occur in the 
> successful run also.
https://www.dropbox.com/s/lm8b8glkw2t9934/rsync64.strace?dl=0
>
> And is it possible for you to create a failing rsync command that 
> others could try to replicate?  There would be a better chance of 
> debugging this if I could run a failing rsync command under gdb.
I will directly email you a ZIP of the folder.  It's not big (some small 
HTML files the guy manages) and a few script files.
>
> I noticed some things about your PATH in the cygcheck output that you 
> posted.
>
> 1. Your PATH is very long.  Could you try simplifying it to see if 
> that helps? For example,
>
>   PATH=/usr/bin rsync...
Hmm, I can try.
>
> 2. Your PATH contains the /bin directories from both your 32-bit and 
> your 64-bit Cygwin installations.  I don't know if that's part of your 
> problem, but it's worth checking.
Yeah, this machine I normally run the 64 bit versions, but just opened a 
shell and prepended the 32 bit dir to test.
>
> 3. You have an environment variable APTH that looks suspiciously like 
> your PATH.  This may be irrelevant, but you probably don't want that.

That was me fatfingering #2