Mailing-List: contact harmony-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Message-ID: <2737149.1158037523840.JavaMail.jira@brutus>
Date: Mon, 11 Sep 2006 22:05:23 -0700 (PDT)
From: "Alexey Varlamov (JIRA)" <jira@apache.org>
To: harmony-commits@incubator.apache.org
Subject: [jira] Updated: (HARMONY-1258) [drlvm][kernel] Incorrect detection
 of privileged and reflection frames in
 Java_org_apache_harmony_vm_VMStack_getClasses
In-Reply-To: <29375444.1156244173936.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/HARMONY-1258?page=all ]

Alexey Varlamov updated HARMONY-1258:
-------------------------------------

    Attachment: H-1258.patch

The fix is provided now.

> [drlvm][kernel] Incorrect detection of privileged and reflection frames in Java_org_apache_harmony_vm_VMStack_getClasses
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-1258
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1258
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Alexey Varlamov
>         Attachments: H-1258.patch
>
>
> The API contract of o.a.h.vm.VMStack.getClasses(int maxSize, boolean considerPrivileged) requires special handling of reflection and privileged frames of Java stack, but detection mechanism is buggy:
> 1) Only 1 of 4 j.s.AccessController.doPrivileged() methods is recognized (which one depends on bootstrap sequence (!) );
> 2) j.l.reflect.Constructor.newInstance() is not considered as reflection frame.
> Also, currently this method is used only by j.s.AccessController, with the same arguments getClasses(-1, true). This method may worth to be re-designed.
> The fix will follow later.

-- 
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