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
Message-Id: <5.1.0.14.2.20020419000230.02e3b708@pop.asw.cz>
X-Sender: jindroush AT pop3 DOT seznam DOT cz
Date: Fri, 19 Apr 2002 00:03:29 +0200
To: cygwin AT cygwin DOT com
From: Jindroush <jindroush AT seznam DOT cz>
Subject: Asynchronous exceptions
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi,

anybody has working example of catching asynchronous exceptions on
cygwin 2.95-3?

I tried:

int main()
{
         try
         {
                 BadFunc();
         }
         catch(...)
         {
                 printf( "Badfunc was really bad!\n" );
         }
}

void BadFunc()
{
         BYTE* p = NULL;
         *p = 0;
}

Althought I complied with -fexceptions -fasynchronous-exceptions, it
just prints out the cygwin/gcc runtime error message and produces stack
dump.

Does cygwin support that?

Jindroush (jindroush AT seznam DOT cz)
http://jindroush.atari.org - Home of Atari Cartridge Dumping Project.


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