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
Message-ID:	<018d01c2484c$e4fdd530$6132bc3e@BABEL>
From:	"Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To:	<cygwin-developers AT cygwin DOT com>
References:	<20020816201318 DOT GA24942 AT redhat DOT com> <122196589420 DOT 20020817171040 AT gmx DOT net> <004f01c2460c$f0242e10$6132bc3e AT BABEL> <20020817170632 DOT GA1632 AT redhat DOT com>
Subject:	Re: eliminated reliance on newlib malloc
Date:	Tue, 20 Aug 2002 14:24:20 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

[Sorry for the slow response but my email's been ailing all
weekend]

"Christopher Faylor" <cgf AT redhat DOT com> wrote:
> I don't build on cygwin.  Never have.

Sensible man.

> There is a snapshot up there now.

The second version of the new malloc fixed that problem, thanks.
Since then I've seen one crash in make (tho' I've since lost the
core dump in a cleanup), which was inside one of the system DLLs
called from sbrk, as I recall.  It hasn't happened again (and I've
done a few rebuilds since then) so that isn't of much help.
Otherwise all is fine and dandy now.

Cheers,

// Conrad

- Raw text -