Are non-SJLJ exceptions busted on linux/x86?

Thu Nov 17 20:25: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.
My previous related posts:
 http://gcc.gnu.org/ml/java/2005-11/msg00230.html
 http://gcc.gnu.org/ml/java/2005-11/msg00229.html
I'm using this software:
 gij (GNU libgcj) version 4.1.0 20051116 (experimental)
 (revision 107090 from SVN, checked out 2005年11月16日)
 gcj (GCC) 4.1.0 20051116 (experimental)
 (same sources)
 Linux version 2.6.8.1-10mdk
 (cpu is Pentium 4)
My original gcc configuration, which works fine with gcc-4_0-branch from
July
 ../gcc/configure
 --prefix=/var/local/gcc/tip_20051115
 --mandir=/var/local/gcc/man
 --infodir=/var/local/gcc/info
 --enable-shared
 --enable-threads=posix
 --disable-checking
 --host=i386-redhat-linux
 --enable-java-awt=xlib
 --enable-libgcj
 --enable-languages=c,c++,java
 --with-system-zlib
 --enable-__cxa_atexit