GCJ/minGW produced executables and linux/wine

[Ranjit Mathew]

>  > 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.
> 
> Indeed.  Has gcj on that target ever worked with DWARF2 exceptions?

Yes, statically linked executables do work fine. Only interpreted
programs have problems due to the reason (I strongly believe) cited
above.


>  > And without all the recent patches for addr2line
>  > and c++filt (*ahem* Andrew ;-)) backtraces wouldn't work either.
> 
> Ah, you're still waiting on those.  Sorry.  One problem is that I
> can't test them.  Is it true that although you have done the FSF
> paperwork, you don't have write access?

Yes, I have done the paperwork but I refused the write access when
Tom offered this to me because I believe (as do others, including
Linus) that write access to the CVS should only be with a small
group of solid, trustworthy individuals. That way you can ensure
the quality and security of the code being checked in. BTW, Tom
did offer only write-on-approval access, but I believe the rigour
is more when the maintainers approve and commit themselves.

    http://gcc.gnu.org/ml/gcc/2002-12/msg00800.html

Maybe I'm misguided here, but still, this is what I think.

The flip side is that my patches get approved/rejected only when
you/Tom get around to examining, approving, testing and committing
them. But that's OK by me - I just hope that minor pings from
my side don't turn to harrassments for you guys, that's all.

Ranjit.

-- 
Ranjit Mathew        Email: rmathew AT hotmail DOT com
Bangalore,           
INDIA.               Web: http://ranjitmathew.tripod.com/