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
Message-Id:	<3.0.5.32.20031231100244.0082ad10@verizon.net>
X-Sender:	phumblet AT verizon DOT net (Unverified)
Date:	Wed, 31 Dec 2003 10:02:44 -0500
To:	cygwin AT cygwin DOT com
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Subject:	Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
Mime-Version:	1.0

Christopher Faylor wrote:
>>Oh.  This is probably with current CVS, which is broken.  Known problem.
>>It's why I haven't generated a snapshot yet.

>This should be fixed now.  I'm uploading a snapshot.

CYGWIN_ME-4.90 hpn5170x 1.5.6s(0.108/3/2) 20031231 01:31:40 i686 unknown
unknown Cygwin

Now virtually every cygwin program (/bin/true, ls, uname,...) almost
always ends with the popup about causing an error in Cygwin1.dll. 

Pierre

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

- Raw text -