harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Cornwall (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-5573) [classlib][pack200] Caught exceptions may not resolve correctly
Date Wed, 05 Mar 2008 00:13:40 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Cornwall updated HARMONY-5573:
-------------------------------------

    Attachment: main-good.patch

Deleted main.patch (which was bad) and attached main-good.patch (which is safe to apply).
Please apply main-good.patch to the build.

> [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
>         Environment: All Pack200
>            Reporter: Andrew Cornwall
>         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.


Mime
View raw message