Are non-SJLJ exceptions busted on linux/x86?

Andrew Haley aph@redhat.com
Fri Nov 18 11:28:00 GMT 2005


Scott Gilbertson writes:
 > Is something busted in the non-SJLJ unwind mechanism with recent
 > builds for linux/x86? 
No.
 > 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)
Works for me.
gcc version 4.1.0 20051115 (experimental)
GNU ld version 2.16.91 20051117
Linux 2.6.11-1.1369_FC4
Andrew.


More information about the Java mailing list

AltStyle によって変換されたページ (->オリジナル) /