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] Commented: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run in lazy resolution mode with JET
Date Sat, 09 Jun 2007 05:23:26 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503015
] 

Alexey Varlamov commented on HARMONY-4016:
------------------------------------------

Mikhail,
I tested  lazy_fix2.diff on Linux debug build and the following tests fail for me:
HUT:
org.apache.harmony.security.tests.java.security.serialization.BasicPermissionCollectionTest
FAILED
org.apache.harmony.security.tests.java.security.serialization.PermissionsTest FAILED
org.apache.harmony.security.tests.java.security.serialization.UnresolvedPermissionCollectionTest
FAILED
org.apache.harmony.security.tests.java.security.serialization.UnresolvedPermissionTest FAILED
org.apache.harmony.security.tests.x509.PolicyQualifierInfoTest FAILED
smoke:
[echo] *** FAILED **** : gc.RunFinalizersOnExitTest (0 res code)


> [drlvm][jit] gc.Mark fails when run in lazy resolution mode with JET
> --------------------------------------------------------------------
>
>                 Key: HARMONY-4016
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4016
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>            Assignee: Alexey Varlamov
>         Attachments: lazy_fix.diff, lazy_fix2.diff
>
>
> I've found that gc.Mark fails when lazy resolution mode is on.
> the reason is that all VM helpers for lazy mode do not protect managed operands and these
operands become outdated when GC enumeration happens.

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


Mime
View raw message