From: "Aaron W. LaFramboise" <aaronavay62@aaronwl.com>
To: Danny Smith <dannysmith@users.sourceforge.net>
Cc: gcc@gcc.gnu.org, Cygwin <cygwin@cygwin.com>,
mingw-dvlpr <mingw-dvlpr@lists.sourceforge.net>
Subject: Re: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH
Date: Wed, 24 Nov 2004 06:34:00 -0000 [thread overview]
Message-ID: <41A3FE7A.60005@aaronwl.com> (raw)
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
next prev parent reply other threads:[~2004-11-24 3:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 22:41 Danny Smith
2004-11-24 0:47 ` Richard Henderson
2004-11-24 7:08 ` Ranjit Mathew
2004-11-24 8:08 ` Danny Smith
2004-11-24 8:26 ` Richard Henderson
2004-11-24 9:41 ` Aaron W. LaFramboise
2004-11-24 17:40 ` Richard Henderson
2004-11-24 18:19 ` Andrew Haley
2004-11-24 8:40 ` Danny Smith
2004-11-24 19:00 ` Richard Henderson
2004-11-24 19:57 ` Andrew Pinski
2004-11-24 20:02 ` Richard Henderson
2004-11-24 21:23 ` Danny Smith
2004-11-24 6:34 ` Aaron W. LaFramboise [this message]
2004-11-24 6:58 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41A3FE7A.60005@aaronwl.com \
--to=aaronavay62@aaronwl.com \
--cc=cygwin@cygwin.com \
--cc=dannysmith@users.sourceforge.net \
--cc=gcc@gcc.gnu.org \
--cc=mingw-dvlpr@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).