Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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:	<41A3FE7A.60005@aaronwl.com>
Date:	Tue, 23 Nov 2004 21:22:34 -0600
From:	"Aaron W. LaFramboise" <aaronavay62 AT aaronwl DOT com>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
MIME-Version:	1.0
To:	Danny Smith <dannysmith AT users DOT sourceforge DOT net>
CC:	gcc AT gcc DOT gnu DOT org, Cygwin <cygwin AT cygwin DOT com>,
	mingw-dvlpr <mingw-dvlpr AT lists DOT sourceforge DOT net>
Subject:	Re: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH
References:	<001701c4d1ab$949322e0$0a6d65da AT DANNY>
In-Reply-To:	<001701c4d1ab$949322e0$0a6d65da@DANNY>

Danny Smith wrote:

> If a C library function that takes a callback arg is compiled
> using stdcall convention, C++ exception thrown by the callback
> result in abort.

Just to speculate while not asking anyone to implement anything, would
there be any value in implementing special behavior when throwing
through non-dwarf2 code, such as checking for an SEH handler on the
stack, or use the MSVC unwinding routines (which MinGW has access to, I
beleive)?

Do any Windows system routines have any function local cleanup that
they'd need to do registered with SEH, or are they OK with suddenly
being zapped out of existance at user code call points?

Aaron W. LaFramboise


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

- Raw text -