Subject: RE: GCC 3.3-Signal 11
From: "Robert McNulty Junior" <[email-masked]>
To: "Kelley Cook" <[email-masked]>, <[email-masked]>
Cc: <[email-masked]>
Date: Thu, 6 Feb 2003 23:59:00 -0600

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: [email-masked] [mailto:[email-masked]]On Behalf Of
Kelley Cook
Sent: Thursday, February 06, 2003 11:15 PM
To: [email-masked]
Cc: [email-masked]
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 <[email-masked]>, 
KelleyCook=[email-masked] 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/