This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
try {} finally {}
- To: java at gcc dot gnu dot org
- Subject: try {} finally {}
- From: Tony Kimball <alk at pobox dot com>
- Date: Wed, 18 Jul 2001 11:12:01 -0500
- Reply-To: alk at pobox dot com
I have seen enough instances of this behaviour so that I am fairly
certain that the bug I am about to describe exists; however, I have
not been able to produce a small case. This is probably the same
bug that Martin Kahlert was trying to isolate. I hope that I can
contribute a somewhat better characterization of the bug, if nothing else:
When there is a try {} finally {} block, with no catch clause,
sometimes exception.cc:get_ttype_entry will return null. This results
in a segv in _Jv_IsAssignableFrom during a throw, which sometimes will
recursively segv in the handler.
I am using the 3.0.1 branch.