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
Reply-To:	<nhv AT cape DOT com>
From:	"Norman Vine" <nhv AT cape DOT com>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	RE: I know CVS is hosed (this time for sure)
Date:	Fri, 7 Sep 2001 19:08:43 -0400
Message-ID:	<000e01c137f2$0b795980$a300a8c0@nhv>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook 8.5, Build 4.71.2232.26
In-Reply-To:	<20010907173823.A4187@redhat.com>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
Importance:	Normal

Christopher Faylor writes:
>
>Ok, I managed to duplicate this.  It didn't happen to me when building
>in the winsup directory but it did in the top level.
>
>The problem was, as I suspected, due to the zombies allocation.  The
>problem is that allocating the zombies array only when needed 
>caused the
>heap to grow while the program was in the process of forking.  So,
>when the parent tried to copy the heap to the child during a fork, the
>heap was larger in the parent than in the child.  Boom.
>
>That illustrates potential thread unsafety in fork() but I'm sure not
>going to fix that before 1.3.3.
>
>AFAICT, this also had nothing to do with moving buckets to 
>cygheap.  I'm
>not sure how that would have affected anything unless the alignment in
>the data segment caused by having buckets there threw off the heap just
>enough so that it masked the fork problem.
>
>Corinna and Egor, can you verify if this checkin fixes things.

Chris

I didn't want to chime in with a 'me too' before but I had been getting 
'spawning' errors with the CVS cygwin for the last couple of days.  

The current CVS files seem to work fine !!  

I can bootstrap Cygwin again  :-)

Thanks

Norman Vine

- Raw text -