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
From: "Robert McNulty Junior" <bmj2001 AT bellsouth DOT net>
To: "Kelley Cook" <KelleyCook AT comcast DOT net>, <gcc AT gcc DOT gnu DOT org>
Cc: <cygwin AT cygwin DOT com>
Subject: RE: GCC 3.3-Signal 11
Date: Thu, 6 Feb 2003 23:59:00 -0600
Message-ID: <GGEKKFKDCKKAHNCJOFCNGELGCAAA.bmj2001@bellsouth.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
In-Reply-To: <MPG.18ad0af1c8355ca8989687@news.gmane.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal

I know. 20030502 works fine for now.
No more signal 11 (error 123 I think was the other one)
Going further, you can see where some names are used, but not defined.


-----Original Message-----
From: gcc-owner AT gcc DOT gnu DOT org [mailto:gcc-owner AT gcc DOT gnu DOT org]On Behalf Of
Kelley Cook
Sent: Thursday, February 06, 2003 11:15 PM
To: gcc AT gcc DOT gnu DOT org
Cc: cygwin AT cygwin DOT com
Subject: Re: GCC 3.3-Signal 11


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