This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: I know CVS is hosed (this time for sure)


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]