Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <038a01c1b085$e8ac4ef0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Andreas Damm" , References: Subject: Re: libgcc exception handling not thread safe Date: Fri, 8 Feb 2002 20:49:31 +1100 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 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 08 Feb 2002 09:49:04.0985 (UTC) FILETIME=[D857B490:01C1B085] === ----- Original Message ----- From: "Andreas Damm" To: Sent: Friday, February 08, 2002 8:47 PM Subject: libgcc exception handling not thread safe > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > libgcc.a in the gcc package does not seem to be thread safe with regards > to c++ exception handling. Doing a nm libgcc.a does not show any > dependencies on Windows synchronisation and thread functions (e.g. > InterlockedIncrement and TlsAlloc). > > When compiling a c++ program with -mno-cygwin which runs multiple threads > it will eventually crash. > > Should this be fixed? No. Libgcc.a is a cygwin application, and is not meant to be linked in with -mno-cygwin compiles. A mingw libgcc.a is needed for that scenario. Rob -- 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/