Re: GCJ/minGW produced executables and linux/wine

["Ranjit Mathew" <rmathew4lists at hotmail dot com>]

> Jeff Sturm writes:
>  > On Tue, 4 Mar 2003, Andrew Haley wrote:
>  > >  > FAIL: Throw_2 -O execution - bytecode->native test
>  > >
>  > > Your exception handling is totally busted.
>  > 
>  > Indeed.  Do we now need -fcheck-references even on a sjlj-target?

Is it *really* built as an SJLJ target? I mean, unless you specify
"--enable-sjlj-exceptions" explicitly during GCC configuration, it
builds as a DWARF-2 EH using target. In which case exceptions would
not work in the interpreter at all without DW2 EH information in
libffi for Win32. And without all the recent patches for addr2line
and c++filt (*ahem* Andrew ;-)) backtraces wouldn't work either.


> It is legal to longjmp from a signal handler.  However, as I
> understand it (and I understand very little about Windows APIs) this
> isn't exactly a signal handler.

*Which* signal handler are we talking about here?

 
> So, maybe who has the docs can tell us: is it legal to longjmp from a
> Windows exception handler?

Google: "<your query> site:msdn.microsoft.com"

:-P

Ranjit.