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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Kelley Cook Subject: Re: GCC 3.3-Signal 11 Date: Fri, 7 Feb 2003 00:15:18 -0500 Lines: 21 Message-ID: References: X-Complaints-To: usenet@main.gmane.org X-Newsreader: MicroPlanet Gravity v2.60 X-Archive: encrypt Cc: gcc@gcc.gnu.org [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/