Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <9532500.1167348262495.JavaMail.jira@brutus>
Date: Thu, 28 Dec 2006 15:24:22 -0800 (PST)
From: "Gregory Shimansky (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-2917) [drlvm][jvmti][em64t] Incorrect
 JVMTI monitor exit stub
In-Reply-To: <33386608.1167343941051.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-2917?page=comments#action_12461271 ] 
            
Gregory Shimansky commented on HARMONY-2917:
--------------------------------------------

While JVMTI implementation was not yet designed for x86_64, this case might be a real bug in threading implementation and could be fixed without heavy changes in components like JIT. OHOH LIL for x86_64 might be lacking some functionality too.

> [drlvm][jvmti][em64t] Incorrect JVMTI monitor exit stub
> -------------------------------------------------------
>
>                 Key: HARMONY-2917
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2917
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: em64t
>            Reporter: Ilya Berezhniuk
>
> When JVMTI is enabled, rth_get_lil_monitor_exit_generic() function generates special stub version for monitor exit.
> But LIL code for JVMTI is incorrect, so assertion occurs on lil_is_valid() check.

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