Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Robert McNulty Junior" To: "Kelley Cook" , Cc: Subject: RE: GCC 3.3-Signal 11 Date: Thu, 6 Feb 2003 23:59:00 -0600 Message-ID: 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: 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@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 , 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 -- 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/