Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
From: "Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To: <cygwin-developers AT cygwin DOT com>
Subject: RE: 1.3.20
Date: Sat, 1 Feb 2003 19:55:48 -0600
Message-ID: <NCBBIHCHBLCMLBLOBONKGEPADLAA.g.r.vansickle@worldnet.att.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
In-Reply-To: <20030201041117.GA20843@redhat.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal

> Given my botch in passwd.cc, we should probably release a new version
> of cygwin ASAP.
>
> Besides Pierre's outstanding ntsec problems, are there other issues that
> would hold up a release?
>

As of Friday I was still having that "Signal 11" problem building gcc (HEAD from
cvs) on Cygwin that I and I think one other guy reported on cygwin@.  I haven't
had time to narrow it down any further than I did in
http://cygwin.com/ml/cygwin/2003-01/msg01617.html (basically "it's dying in
vasprintf()").  1.3.18 works, .19 and all snapshots since do not.  It'd be
tomorrow at the earliest that I'd be able to do anything further on this (I'd
have to go in to work and do it, the ol' 20GB hard drive here at home
overfloweth).

--
Gary R. Van Sickle
Brewer.  Patriot.