This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Interpreter aborts when it should have handled an exception
- From: Bryce McKinlay <mckinlay at redhat dot com>
- To: Scott Gilbertson <scottg at mantatest dot com>
- Cc: java at gcc dot gnu dot org
- Date: Wed, 16 Nov 2005 18:32:51 -0500
- Subject: Re: Interpreter aborts when it should have handled an exception
- References: <308a01c5eaf9$b6d11840$3c16a8c0@mantatest.com>
Scott Gilbertson wrote:
I've had this sort of problem with several recent gcc builds. The
interpreter aborts when the code should have caught an exception.
Are others seeing the same problem?
Anybody know what's going on?
I could not reproduce this using the latest svn trunk.
It does seem odd that the program would crash when 'Hello' is
interpreted, but not when natively compiled, because the interpreter is
not being touched here - both the throw and catch are in compiled libgcj
code. I think this is just the result of VMCompiler bringing a lot more
code into the application startup path - ie MD5 which causes security
provider initialization, and that calls into java.util.logging, etc.
Bryce