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
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: Kelley Cook <KelleyCook AT comcast DOT net>
Subject: Re: GCC 3.3-Signal 11
Date: Fri, 7 Feb 2003 00:15:18 -0500
Lines: 21
Message-ID: <MPG.18ad0af1c8355ca8989687@news.gmane.org>
References: <GGEKKFKDCKKAHNCJOFCNGEDMCAAA DOT bmj2001 AT bellsouth DOT net> <MPG DOT 18acf893146192bc989686 AT news DOT gmane DOT org>
X-Complaints-To: usenet AT main DOT gmane DOT org
X-Newsreader: MicroPlanet Gravity v2.60
X-Archive: encrypt
Cc: gcc AT gcc DOT gnu DOT org

[This followup was posted to gmane.comp.gcc.devel and a copy 
was sent to the cited author.]

In article <MPG DOT 18acf893146192bc989686 AT news DOT gmane DOT org>, 
KelleyCook=Wuw85uim5zDR7s880joybQ AT public DOT gmane DOT org says...
> It's not a GCC problem.
> 
> Cygwin 1.3.19 added in support for vasprintf (previously GCC 
> would use the version included in libiberty).  
> 
> Unfortunately, Cygwin's (actually newlib's) vasprintf is not 
> quite right and it bombs under certain circumstances.  
> Supposedly that bug has been corrected, but it still crashes 
> for me with the Feb 3rd cygwin snapshot.

Namely since after checking the changelog that particular 
patch wasn't put in until the Feb 5th snapshot.

It works now.

Kelley Cook


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