This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: GCC 3.3-Signal 11
- 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>
- Date: Thu, 6 Feb 2003 23:59:00 -0600
- Subject: RE: GCC 3.3-Signal 11
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@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org]On Behalf Of
Kelley Cook
Sent: Thursday, February 06, 2003 11:15 PM
To: gcc@gcc.gnu.org
Cc: cygwin@cygwin.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.18acf893146192bc989686@news.gmane.org>,
KelleyCook=Wuw85uim5zDR7s880joybQ@public.gmane.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