Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Matt <matt AT use DOT net>
X-Sender: matt AT cesium DOT clock DOT org
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Any insight on problems reported in cygwin mailing list?
In-Reply-To: <20000211092852.A11395@cygnus.com>
Message-ID: <Pine.NEB.4.10.10002111143290.7604-100000@cesium.clock.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Date: 	Fri, 11 Feb 2000 12:21:58 -0800

On Fri, 11 Feb 2000, Chris Faylor wrote:

> Can anyone offer any insight on what is going wrong with recent snapshots?
> I suspect that it is somehow w32api related but, since I'm not seeing any
> problems, I can't fix them.
> 
> If someone can give me a repeatable test case (preferably one that fails
> on WinNT) that would be very helpful.

I have been noticing that when I build bison 1.28, the bash I am running
make from will just exit in the middle of it -- sometimes. 2 out of 3
times it completes just fine. I was going to look for some
extraneous calls to exit() or abort() in the code, but haven't gotten
around to it. 

(I was doing this using the default gcc setup that comes with cygwin 1.0,
and the 2/6/2000 snapshot on NT 4.0 SP6)


--
it's only fair to tell you
I'm absolutely cuckoo