Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <064801c1021c$0b915be0$806410ac@local>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT cygwin DOT com>
Subject: Fw: G++, C++ Exception handling, and cygwin
Date: Sun, 1 Jul 2001 20:53:20 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-OriginalArrivalTime: 01 Jul 2001 10:40:54.0049 (UTC) FILETIME=[4DC8B910:01C1021A]


----- Original Message -----
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Constantine Sapuntzakis" <csapuntz AT stanford DOT edu>
Cc: <cygwiin-apps AT cygwin DOT com>
Sent: Sunday, July 01, 2001 8:49 PM
Subject: Re: G++, C++ Exception handling, and cygwin


> Please keep replies cc'd to the list.
>
> Let me know what you find - if yo can provide a reasonable sized testcase
I
> will see what I can do to solve it.
>
> Also, I suggest you use the latest cygwin snapshot - some major
performance
> and reliability improvements have been made to pthreads recently.
>
> Rob
>
> ----- Original Message -----
> From: "Constantine Sapuntzakis" <csapuntz AT stanford DOT edu>
> To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
> Sent: Sunday, July 01, 2001 5:12 AM
> Subject: Re: G++, C++ Exception handling, and cygwin
>
>
> > The pthread-based exception handling seems to interfere with the
> scheduling
> > of threads in my application. I'm not sure why or how this is and will
try
> > to
> > track it down in my free time.
> >
> > -Costa
> >
> > ----- Original Message -----
> > From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
> > To: "Constantine Sapuntzakis" <csapuntz AT Stanford DOT EDU>;
> > <cygwin-apps AT sources DOT redhat DOT com>
> > Sent: Friday, June 15, 2001 7:04 PM
> > Subject: Re: G++, C++ Exception handling, and cygwin
> >
> >
> > > ----- Original Message -----
> > > From: "Constantine Sapuntzakis" <csapuntz AT stanford DOT edu>
> > > To: <cygwin-apps AT sources DOT redhat DOT com>
> > > Sent: Saturday, June 16, 2001 11:46 AM
> > > Subject: G++, C++ Exception handling, and cygwin
> > >
> > >
> > > > The libgcc.a that is distributed with cygwin gcc-2.95.3-4 only
> > > supports
> > > > single threaded C++ exception handling. The library has exception
> > > routines
> > > > that use static variables.
> > > >
> > > > When I  substitute a version of libgcc.a that includes the code in
> > > > gcc/gthr-win32.h, multi-threaded
> > > > C++ apps with exception handling seem to work (we've been running
them
> > > for a
> > > > couple months
> > > > now).
> > > >
> > > > Given that the code seems to be there to do this correctly, why is
it
> > > not
> > > > enabled?
> > >
> > > a) I don't believe therehas been a release of gcc since this was
pointed
> > > out on this list recently.
> > > b) pthreads are the correct thread handlers for cygwin, not win32.
> > > No-one has provided feedback on stability using pthreaded exception
> > > handlers however.
> > >
> > > Rob
> > >
> > > > Thanks,
> > > > Costa
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>