From: "Aaron W. LaFramboise" <aaronavay62@aaronwl.com>
To: Richard Henderson <rth@redhat.com>
Cc: Danny Smith <dannysmith@users.sourceforge.net>,
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 09:41:00 -0000 [thread overview]
Message-ID: <41A44B97.1060007@aaronwl.com> (raw)
In-Reply-To: <20041124080708.GA3578@redhat.com>
Richard Henderson wrote:
> On Wed, Nov 24, 2004 at 08:50:17PM +1300, Danny Smith wrote:
>
>>So is it a general requirements of DW2 EH that functions that are passed
>>callbacks as args be compiled with -fexceptions, if the callbacks may
>>throw?
>
> Yes. Thus glibc compiles e.g. qsort and bsearch with -fexceptions.
Is there a way to have the DW2 unwinder call some particular function,
for eg, if the previous frame was not compiled with -fexceptions, rather
than just crashing? Is this what MD_FALLBACK_FRAME_STATE_FOR is for?
Other Windows compilers are able to handle this condition. I don't know
anything at all about MSVC's non-SEH exception handling, and I have not
done any analysis at all, but it seems likely that these compilers are
unwinding SEH information in foreign frames. If this is the case,
compatibility with this is highly desirable, and perhaps essential for
throwing through system routines that use SEH, which is something other
compilers on the system support.
Aaron W. LaFramboise
next prev parent reply other threads:[~2004-11-24 8:49 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 [this message]
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
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=41A44B97.1060007@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 \
--cc=rth@redhat.com \
/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).