You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Andrew Cornwall (JIRA)" <ji...@apache.org> on 2008/03/05 17:43:40 UTC
[jira] Closed: (HARMONY-5573) [classlib][pack200] Caught exceptions
may not resolve correctly
[ https://issues.apache.org/jira/browse/HARMONY-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Cornwall closed HARMONY-5573.
------------------------------------
Patch applied as expected. Thanks!
Closing issue.
> [classlib][pack200] Caught exceptions may not resolve correctly
> ---------------------------------------------------------------
>
> Key: HARMONY-5573
> URL: https://issues.apache.org/jira/browse/HARMONY-5573
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Environment: All Pack200
> Reporter: Andrew Cornwall
> Assignee: Sian January
> Fix For: 5.0M6
>
> Attachments: main-good.patch
>
>
> It's possible for a class to refer to an exception type in the exception_table only (and not in the body of the method). That is, the class could have a method of the form:
> foo() {
> try {
> // some code that doesn't reference FooException
> }
> catch (FooException ex) {
> }
> If something else in the class refers to FooException, the ClassConstantPool will contain FooException so the exception_table will be able to resolve it. However, if nothing else in the class refers to FooException, the ClassConstantPool will not contain it - so the class will not resolve properly.
> This patch fixes the code so the catch_type is added to the ClassConstantPool so it will always resolve correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.