This is the mail archive of the
mailing list for the Cygwin project.
Re: C++ Exceptions in Multithreaded Applications Crash
- From: Lenny Primak <lprimak at hope dot nyc dot ny dot us>
- To: Lenny Primak <lprimak at hope dot nyc dot ny dot us>
- Cc: Thomas Pfaff <tpfaff at gmx dot net>, cygwin at cygwin dot com
- Date: Wed, 10 Jul 2002 22:21:50 -0400
- Subject: Re: C++ Exceptions in Multithreaded Applications Crash
Seems to be working in the cygwin I d/l on july 1.
Strange... but glad that it works.
Thanks for all your help.
On Wednesday, July 3, 2002, at 04:03 PM, Lenny Primak wrote:
Strange indeed, I will try that, but in the meanwhile,
can you confirm that stock (cygwin.com) build does not work?
Thanks a log
On Wednesday, July 3, 2002, at 03:57 PM, Thomas Pfaff wrote:
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
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
with no results. The following program is used to determine if the
exception context is thread-specific or not:
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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html