Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Mon, 10 Jun 2002 12:51:25 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Latest Snapshot (20020609) Fails Miserably on Win2K
Message-ID:	<20020610165125.GA14989@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<261146618.1023708098@[192.168.70.5]>
Mime-Version:	1.0
In-Reply-To:	<261146618.1023708098@[192.168.70.5]>
User-Agent:	Mutt/1.3.23.1i

On Mon, Jun 10, 2002 at 11:21:38AM -0400, Alan Dobkin wrote:
>FYI, I have been using the nightly cygwin1.dll snapshots for 
>the past week or two, and the one from last night completely 
>fails on my machine (Win2K with current updates).  Reverting 
>to the previous snapshot (20020607) clears up the problem.  
>
>With the latest snapshot, I cannot even open a bash prompt 
>or use any cygwin-linked utilities (i.e. bzip2) from a Win32 
>command prompt.  Launching bash returns the attached trace.
>
>Let me know if you want me to provide more details....

Nope, that seems to pinpoint the problem.  It's in the new thread
code, apparently.  I'll see what I can do to fix this.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -