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
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 3 Jul 2002 21:57:40 +0200 (W. Europe Daylight Time)
From: Thomas Pfaff <tpfaff AT gmx DOT net>
To: Lenny Primak <lprimak AT hope DOT nyc DOT ny DOT us>
cc: cygwin AT cygwin DOT com
Subject: Re: C++ Exceptions in Multithreaded Applications Crash
In-Reply-To: <D61A7C0C-8BAC-11D6-8506-000393640A02@hope.nyc.ny.us>
Message-ID: <Pine.WNT.4.44.0207032153340.-291071@thomas.kefrig-pfaff.de>
X-X-Sender: thomas AT gw DOT kefrig-pfaff DOT de
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AntiVirus: scanned for viruses by NGI Next Generation Internet (http://www.ngi.de/)



On Sat, 29 Jun 2002, Lenny Primak wrote:

> This has been submitted to GCC GNATS as PR/7168.
>
> Using the G++ exception system from multiple threads corrupts the gcc's
> internal exception stack, due to not including the thread-specific
> exception context in the compile.
> GCC Version: 2.95.3-5 from default Cygwin install.
>
> I tried to re-compile gcc with --enable-threads=posix and with
> --enable-sjlj-exceptions
> with no results.  The following program is used to determine if the
> exception context is thread-specific or not:
>
>

Strange:
I have build gcc-2.95.3-5 with --disable-shared --enable-threads
(and without --enable-sjlj-exceptions, but this should be the default)
and i get

func() - eh_context = 970EB0
func() - eh_context = 971368
Great! Exception Stacks Differ.

Thomas


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