Message-ID: <011255E943B4494AB62D316E4532BE99@amber>
From: "Don Ward" <don2387ward@sprynet.com>
To: <cygwin@cygwin.com>
References: <346D8CF793D04BC99A972949F9555CC3@amber> <4C35F33E.60603@gmail.com>
Subject: Re: gcc4: throwing exception from signal handler
Date: Thu, 8 Jul 2010 13:02:28 -0400
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="iso-8859-1";	reply-type=original
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Dave Korn wrote:

> On 08/07/2010 14:01, Don Ward wrote:
>> I would like to be able to catch certain signals (SIGSEGV and SIGSYS)
>> and throw a C++ exception (to be caught in a try/catch construct).  As a
>> simple example:
>
>> Am I misunderstanding how this should work or doing something wrong?  Or
>> is this a problem with Cygwin or gcc?
>
>  Throwing exceptions from a signal handler is a can of worms that requires
> support from both the compiler and the C runtime.

Understood!

>  I was working on adding
> this support for the distro package of gcc-4.5 before I had to go AWOL a
> couple of weeks ago; it requires building the Cygwin DLL with EH tables, 
> and
> adding support in the last-chance stack unwinder in libgcc that is able to
> unwind past our sigfe/sigbe stuff.

I'm glad someone is (or will be) working on it.  In the meanwhile, I can 
make do with gcc 3.4.4.

Thanks,

-- Don W.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple