Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 8 Feb 2002 09:47:04 +0000 (GMT)
From: Andreas Damm <andreas-sourceforge AT radab DOT org>
X-X-Sender:  <dammy AT gate DOT rad-ab DOT u-net DOT com>
To: <cygwin AT cygwin DOT com>
Subject: libgcc exception handling not thread safe
Message-ID: <Pine.LNX.4.33.0202080940190.1281-100000@gate.rad-ab.u-net.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

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


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQE8Y56h6JfsLTFvWG8RAncgAJwNKAJ7vt/YrWbsgQK0hWEManqRJACfam0K
gdn4+z2YYg3PmkF5++9l9YU=
=btR0
-----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/