harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-1561) [DRLVM][interpreter] Wrong access checks in Opcode_PUTFIELD
Date Mon, 25 Sep 2006 05:21:51 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-1561?page=all ]

Alexey Varlamov updated HARMONY-1561:
-------------------------------------

    Attachment: TestPutFinal.j
                TestPutFinalNegative.j

Hmm, JVMS says nothing about methods on stack - it only requires that if a field is final,
it must be declared in the current class.
I've just checked - RI and Jitrino allows to modify final field regardless method names/signatures
provided the class limitation above.
The Jasmin tests are attached.



> [DRLVM][interpreter] Wrong access checks in Opcode_PUTFIELD
> -----------------------------------------------------------
>
>                 Key: HARMONY-1561
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1561
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: All
>            Reporter: Ivan Volosyuk
>         Attachments: putfield.patch, TestPutFinal.j, TestPutFinalNegative.j
>
>
> Interpreter throws IllegalAccessError on putfield opcode for all methods except <init>.
> It should not throw the error if the <init> method for this object is in the calling
stack.
> Reproducible on activemq-4.0.2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message