X-Spam-Check-By: sourceware.org
Message-ID: <438468C5.7070104@byu.net>
Date: Wed, 23 Nov 2005 06:04:05 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: fork problem in latest snapshot on Win98
References: <111720050418 DOT 20954 DOT 437C047D00006256000051DA22064244130A050E040D0C079D0A AT comcast DOT net> <20051122151753 DOT GA17881 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To: <20051122151753.GA17881@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Christopher Faylor on 11/22/2005 8:17 AM:
>>I'm getting a repeatable fork memory allocation error with snapshot
>>20051116 on Win98, when trying to build CVS head of libtool; this was
>>not a problem with 20051020.
> 
> Is this problem still in the latest snapshots?

I upgraded to 20051117, and was able to complete the libtool build on
Win98.  So I guess your change to delay the top-of-stack calculation to
after the setjmp did the trick.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDhGf384KuGfSFAYARAqbhAJ9z5lhAvqky99iWzmMIlylGmj2y/QCgwtqm
EpCF9zkDDpVYstFPVF0UYws=
=GQG3
-----END PGP SIGNATURE-----

--
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/