This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Figured out how to reproduce vfork/rsync bug!
- To: cygwin-developers at cygwin dot com
- Subject: Re: Figured out how to reproduce vfork/rsync bug!
- From: Corinna Vinschen <vinschen at redhat dot com>
- Date: Thu, 6 Sep 2001 16:43:43 +0200
- References: <20010906142836.7323.qmail@lizard.curl.com>
- Reply-To: cygdev <cygwin-developers at cygwin dot com>
On Thu, Sep 06, 2001 at 10:28:36AM -0400, Jonathan Kamens wrote:
> I found some time yesterday (where "found some time" is defined as
> "stayed up until 1:30am") working on tracking this down further. I've
> discovered that it appears to be related to a very long environment
> variable. In particular, if you put this script into a file and run
> it:
>
> #!/bin/sh
>
> export 'INCLUDE=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
> rsync /tmp/foo/ /tmp/bar/
>
> You'll get the Cygwin failure I've previously reported, but if you
> delete one 'x' from the end of the variable setting in the script, the
> failure goes away.
I just tried it desperately another 100 times. I can't reproduce it.
I added x's randomly to make INCLUDE longer than 10 lines, more than
800 x's. Nothing happens.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.