Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: 6 Sep 2001 10:48:15 -0400
Message-ID: <20010906144815.7459.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: cygwin-developers AT cygwin DOT com
CC: cygwin-developers AT cygwin DOT com
In-reply-to: <20010906164343.I537@cygbert.vinschen.de> (message from Corinna
	Vinschen on Thu, 6 Sep 2001 16:43:43 +0200)
Subject: Re: Figured out how to reproduce vfork/rsync bug!
References: <20010906142836 DOT 7323 DOT qmail AT lizard DOT curl DOT com> <20010906164343 DOT I537 AT cygbert DOT vinschen DOT de>

>  Date: Thu, 6 Sep 2001 16:43:43 +0200
>  From: Corinna Vinschen <vinschen AT redhat DOT com>
>  
>  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.

Rats.

Don't bother trying it lots of times.... As far as I can tell, it
either happens every time or doesn't happen at all.

I just discovered another fascinating fact.  If I change my test
script from this:

  #!/bin/sh

  export 'INCLUDE=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
  rsync /tmp/foo/ /tmp/bar/

to this:

  #!/bin/sh

  export 'INCLUDE=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
  cmd /c "rsync /tmp/foo/ /tmp/bar/"

(note the last line) the failure goes away.

This suggests to me that there are problems when getting environment
variables from the parent cygwin process but not when getting them
from the Windows environment.

I'm going to compile the cygwin DLL with malloc debugging and see if
that reveals anything interesting.  While it's compiling, I'm going to
continue to stare intently at the code and see if inspiration strikes
:-).

  jik