This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: Help using gij
- To: Matt Welsh <mdw at cs dot berkeley dot edu>
- Subject: Re: Help using gij
- From: Bryce McKinlay <bryce at albatross dot co dot nz>
- Date: Mon, 08 Nov 1999 17:34:44 +1300
- CC: java-discuss at sourceware dot cygnus dot com, krab at daimi dot au dot dk, green at cygnus dot com
- References: <199911080259.SAA29238@mnemosyne.CS.Berkeley.EDU>
Matt Welsh wrote:
> I am having problems running gij. This appears to be manifesting itself
> in the form of a problem with exception handling.
Use gcc 2.95.2. http://waitaki.otago.ac.nz/~bryce/gcj/
> I have compiled the latest egcs snapshot (02-Nov-1999) and the latest
> libgcj. I did compile libgcj with --enable-interpreter (some documentation
> would have been nice). gij simply crashes when I try to use it. There
> seems to be several problems:
>
> 1) ResourceBundle ends up looking for the class
> gnu.gcj.text.LocaleData_en_US_UNIX
> which doesn't exist -- I copied LocaleData_en_US.java to
> LocaleData_en_US_UNIX.java and built that into libgcj.
AFAIK, it is normal for ResourceBundle to looking for these non-existant files. What is not normal
is for libgcj to crash on a "throw" statement. Unfortunatly this seems to happen all over the place
in the ResourceBundle and Classloading stuff if you compile with recent experimental gcc snapshots.
I have not been able to reproduce this problem in my own code - it only seems to occur for
exceptions thrown and caught _within_ certain parts of libgcj.
This problem is not new - I first reported it a couple of months ago (although perhaps a PR should
be opened...)
Interestingly, putting a statement such as "xxxException x = new xxxException()" before whatever
code in your application is causing libgcj to attempt to throw an exception and crash seems to work
around the problem.
For now, build libgcj with the patched gcc 2.95 and it will all work fine.
regards
[ bryce ]