harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Shimansky (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-1575) [drlvm] [jvmti] Return from java to native and from native to java code needs to be fixed
Date Mon, 25 Sep 2006 22:17:51 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-1575?page=all ]

Gregory Shimansky updated HARMONY-1575:

    Attachment: return-to-and-from-native-fix.patch

Patch to fix the transitions.

> [drlvm] [jvmti] Return from java to native and from native to java code needs to be fixed
> -----------------------------------------------------------------------------------------
>                 Key: HARMONY-1575
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1575
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Gregory Shimansky
>         Attachments: return-to-and-from-native-fix.patch
> I didn't think of so many native-java-native transitions before. It appears that native
is called everywhere in hidden calls to class loader or in explicit calls like System.out.println.

> Single stepping back from java to native requres predicting a next bytecode after *return
one. But there is an assertion that frame is java. If the frame is native it fails. This assertion
was removed because it cannot be satisfied always. But instead I removed incorrect assumption
comments on returning from native code back to Java (it it returns to Java at all) to start
single stepping back in Java code. If the calling code was not Java single stepping won't
happen, it will just wait another native from Java transition.

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


View raw message