Re: libgcc exception handling not thread safe

[Andreas Damm <andreas-sourceforge at radab dot org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok, putting libgcc.a from the Mingw distribution into /lib/mingw seems to
do the trick (another library to salvage from that distribution is
libstdc++.a which also goes into /lib/mingw).


On Fri, 8 Feb 2002, Robert Collins wrote:

> Date: Fri, 8 Feb 2002 20:49:31 +1100
> From: Robert Collins <robert.collins@itdomain.com.au>
> To: Andreas Damm <andreas-sourceforge@radab.org>,
>      "cygwin@cygwin.com" <cygwin@cygwin.com>
> Subject: Re: libgcc exception handling not thread safe
>
>
> ===
> ----- 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
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQE8Y6Ip6JfsLTFvWG8RAhlMAJwMpBpNtf43Jk+lA4AP9Q65dsMd0wCfSuzI
GLN/rYjFKIeNjtpS9GAkAyE=
=uNek
-----END PGP SIGNATURE-----



--
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/