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 Message-ID: <01bd01c0f608$bb285dd0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Constantine Sapuntzakis" , References: <023d01c0f606$2f22a450$934940ab AT KEALIACSAPUNTZ> Subject: Re: G++, C++ Exception handling, and cygwin Date: Sat, 16 Jun 2001 12:04:51 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 16 Jun 2001 01:54:26.0746 (UTC) FILETIME=[461689A0:01C0F607] ----- Original Message ----- From: "Constantine Sapuntzakis" To: Sent: Saturday, June 16, 2001 11:46 AM Subject: G++, C++ Exception handling, and cygwin > 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? a) I don't believe therehas been a release of gcc since this was pointed out on this list recently. b) pthreads are the correct thread handlers for cygwin, not win32. No-one has provided feedback on stability using pthreaded exception handlers however. Rob > Thanks, > Costa > >