This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH
- From: "Aaron W. LaFramboise" <aaronavay62 at aaronwl dot com>
- 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>
- Date: Tue, 23 Nov 2004 21:22:34 -0600
- Subject: Re: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH
- References: <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/