Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Fri, 15 Jun 2001 22:03:24 -0400 From: Christopher Faylor To: cygwin-apps AT sources DOT redhat DOT com Subject: Re: G++, C++ Exception handling, and cygwin Message-ID: <20010615220324.B509@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT sources DOT redhat DOT com References: <023d01c0f606$2f22a450$934940ab AT KEALIACSAPUNTZ> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <023d01c0f606$2f22a450$934940ab@KEALIACSAPUNTZ>; from csapuntz@stanford.edu on Fri, Jun 15, 2001 at 06:46:38PM -0700 On Fri, Jun 15, 2001 at 06:46:38PM -0700, Constantine Sapuntzakis wrote: >The libgcc.a that is distributed with cygwin gcc-2.95.3-4 only supports >single threaded C++ exception handling. The library has exception routines >that use static variables. > >When I substitute a version of libgcc.a that includes the code in >gcc/gthr-win32.h, multi-threaded >C++ apps with exception handling seem to work (we've been running them for a >couple months >now). > >Given that the code seems to be there to do this correctly, why is it not >enabled? As I have repeatedly explained in the past. Any time you find anything not included in any package for cygwin, you can safely assume that it is for one reason and one reason only: Because we're just plain mean. cgf