delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/08/09/23:57:15

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 9 Aug 2005 23:57:04 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Rsync over SSH dies before it is able to send with lots of files
Message-ID: <20050810035704.GA13920@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <42FA081C DOT 25957 DOT 24F4EADF AT localhost> <42F9777B DOT 5080206 AT byu DOT net> <20050810035600 DOT GA13381 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
In-Reply-To: <20050810035600.GA13381@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.8i

On Tue, Aug 09, 2005 at 11:56:00PM -0400, Christopher Faylor wrote:
>On Tue, Aug 09, 2005 at 09:41:47PM -0600, Eric Blake wrote:
>>> - Mounted the directory that I'm copying from elsewhere and made it  
>>> executable (worth a crack) 
>>
>>The only difference you might make to get a larger command line argument
>>length is to make rsync's directory mounted executable (not the directory
>>you are copying).  But if bash is crashing instead of creating a command
>>line that long in the first place, there's no hope to this attempt.
>>
>>> 
>>> bash-3.00$ cat bash.exe.stackdump 
>>> Exception: STATUS_ACCESS_VIOLATION at eip=610022AE 
>>> eax=61259000 ebx=61259000 ecx=FFFF0000 edx=61259048  
>>> esi=00000006 edi=0022E810 
>>> ebp=0022DC08 esp=0022DC00 program=C:\cygwin\bin\bash.exe, pid  
>>> 2748, thread main 
>>> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023 
>>> Stack trace: 
>>> Frame     Function  Args 
>>> 0022DC08  610022AE  (00000012, 00000000, 0022DC28, 0022E820) 
>>
>>Unfortunately, since both bash and cygwin are stripped, this stack trace
>>is relatively useless.  cgf has been working on adding support for .dbg
>>libraries, which can be placed separately from stripped images, to make a
>>stack trace worthwhile.
>
>Right.  So downloading a recent snapshot might prove instructive.  Once
>that's done, anyone can decode the stacktrace with the .dbg file.
>
>It sounds like this may be tickling the same bug as the Postgres problem
>and so, the snapshot might actually fix the problem.
>
>http://cygwin.com/snapshots/
>
>and, if it still doesn't work, the stacktrace and cygcheck output
>attached as per http://cygwin.com/problems.html would be required.

Oh, and I forgot to mention that I agree with Eric that getting rid of
the wildcard on the command line is definitely a good idea and may solve
the problem.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019