From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29710 invoked by alias); 7 Feb 2003 05:15:17 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 29703 invoked from network); 7 Feb 2003 05:15:17 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by 172.16.49.205 with SMTP; 7 Feb 2003 05:15:17 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 18h0p6-0000Oy-00 for ; Fri, 07 Feb 2003 06:13:12 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gcc@gcc.gnu.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 18h0p5-0000Oj-00 for ; Fri, 07 Feb 2003 06:13:11 +0100 From: Kelley Cook Subject: Re: GCC 3.3-Signal 11 Date: Fri, 07 Feb 2003 05:15:00 -0000 Message-ID: References: X-Complaints-To: usenet@main.gmane.org X-Newsreader: MicroPlanet Gravity v2.60 X-Archive: encrypt Cc: cygwin@cygwin.com X-SW-Source: 2003-02/txt/msg00324.txt.bz2 [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