This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: libgcc exception handling not thread safe
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Andreas Damm" <andreas-sourceforge at radab dot org>,<cygwin at cygwin dot com>
- Date: Fri, 8 Feb 2002 20:49:31 +1100
- Subject: Re: libgcc exception handling not thread safe
- References: <Pine.LNX.4.33.0202080940190.1281-100000@gate.rad-ab.u-net.com>
===
----- Original Message -----
From: "Andreas Damm" <andreas-sourceforge@radab.org>
To: <cygwin@cygwin.com>
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/