X-Spam-Check-By: sourceware.org
Date: Tue, 2 May 2006 00:40:21 +0200 (MET DST)
From: Angelo Graziosi <Angelo DOT Graziosi AT roma1 DOT infn DOT it>
To: cygwin AT cygwin DOT com
Subject: Re: Fixing the state of C++ in Cygwin
Message-ID: <Pine.OSF.4.21.0605020032220.1060-100000@ax0rm1.roma1.infn.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com



Steven Brown wrote:


> As an example of why just patching the headers won't work, try to
> compile and run my old weirdbug[1] example - type make and run
> xxx-cygwin.exe. If it aborts, the problem still exists on your system. I
> just tested it, and as expected, simply patching the files like that
> didn't fix it.

I confirm! Your test case aborts if compiled with GCC-3.4.4+onlyPR24196 to
basic_string*.

Your test case DOES NOT abort if one builds it with GCC that was rebuilt
whitout that patch but configured with --enable-fully-dynamic-string!


Thanks,

   Angelo.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/