Are non-SJLJ exceptions busted on linux/x86?

Thu Nov 17 20:29:00 GMT 2005

>> Is something busted in the non-SJLJ unwind mechanism with recent builds for
> linux/x86? If so, perhaps --enable-sjlj-exceptions should be the default on
> that platform. If not, is there some dependency I need to make it work?
>> With recent trunk, my dynamic executables work but static and interpreted
> both fail, as I mentioned in earilier posts referenced below. These appear
> to be two cases of the same problem, namely that throw/catch only works with
> dynamic executables. I was able to solve it by
> adding --enable-sjlj-exceptions to my configuration. That makes the
> interpreter work fine, although I now get a segv in _Jv_FreeMethodCache on
> exit with the static build -- separate issue I think.

dwarf2 exceptions are only ever required to work with dynamic linking as
there needs to be only one unwind functions and data.
Why are yiou trying to static link with gcj? Seems like you are making a big
issue in general.
Thanks,
Andrew Pinski