harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vera Volynets (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-3134) [drlvm][classloader] Different condition of checks for system and user classloader
Date Mon, 19 Feb 2007 11:53:05 GMT

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

Vera Volynets updated HARMONY-3134:

    Attachment: consider-Xverify_20060219.patch

This patch fixes the problem.
In case class is loaded by user defined classloader all checks are mundatory and optional
in clase of sytem classloader.

> [drlvm][classloader] Different condition of checks for system and user classloader
> ----------------------------------------------------------------------------------
>                 Key: HARMONY-3134
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3134
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Vera Volynets
>            Priority: Minor
>         Attachments: consider-Xverify_20060219.patch, method.class, method.java, test_method.java
> Java specification apply restrictions on field and method names.
> I've noticed that if class is loaded by system Classloader this checks are optional and
are on in case -Xverify option in command line is set.
> And if class is loaded by user class, this checks are  mandatory.
> Our machine makes field and method name checks only if -Xverify flag is set, so there
is no accordance with RI.
> This is valid for classfile version 45 and 49.
> I've attached patch with test and class with spoiled method name.
> To run this test:
> ./java.exe test_method method

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message