You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Mikhail Fursov (JIRA)" <ji...@apache.org> on 2007/05/31 16:51:15 UTC
[jira] Created: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
[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
Attachments: lazy_fix.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.
[jira] Updated: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov updated HARMONY-4016:
------------------------------------
Attachment: lazy_fix.diff
> [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
> Attachments: lazy_fix.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.
[jira] Closed: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov closed HARMONY-4016.
-----------------------------------
> [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: Mikhail Fursov
> Attachments: lazy_fix.diff, lazy_fix2.diff, lazy_fix3.diff, lazy_fix4.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.
[jira] Assigned: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov reassigned HARMONY-4016:
---------------------------------------
Assignee: Mikhail Fursov (was: Alexey Varlamov)
> [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: Mikhail Fursov
> Attachments: lazy_fix.diff, lazy_fix2.diff, lazy_fix3.diff, lazy_fix4.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.
[jira] Assigned: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov reassigned HARMONY-4016:
----------------------------------------
Assignee: Alexey Varlamov
> [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
>
>
> 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.
[jira] Commented: (HARMONY-4016) [drlvm][jit] gc.Mark fails when
run in lazy resolution mode with JET
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503016 ]
Alexey Varlamov commented on HARMONY-4016:
------------------------------------------
The gc.RunFinalizersOnExitTest failure appears intermittently, probably even w/o the patch.
> [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.
[jira] Updated: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov updated HARMONY-4016:
------------------------------------
Attachment: lazy_fix2.diff
lazy_fix2.diff: NPE check added for invokes.
> [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.
[jira] Commented: (HARMONY-4016) [drlvm][jit] gc.Mark fails when
run in lazy resolution mode with JET
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HARMONY-4016) [drlvm][jit] gc.Mark fails when
run in lazy resolution mode with JET
Posted by "Pavel Pervov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500389 ]
Pavel Pervov commented on HARMONY-4016:
---------------------------------------
The fix is neat. Thanks.
> [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
> Attachments: lazy_fix.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.
[jira] Updated: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov updated HARMONY-4016:
------------------------------------
Attachment: lazy_fix4.diff
lazy_fix4.diff: the fix without turning lazy mode on.
> [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, lazy_fix3.diff, lazy_fix4.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.
[jira] Updated: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov updated HARMONY-4016:
------------------------------------
Attachment: lazy_fix3.diff
lazy_fix3.diff: the problems found by Alexei Varlamov was fixed.
> [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, lazy_fix3.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.
[jira] Resolved: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov resolved HARMONY-4016.
-------------------------------------
Resolution: Fixed
Committed revision 548294
> [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: Mikhail Fursov
> Attachments: lazy_fix.diff, lazy_fix2.diff, lazy_fix3.diff, lazy_fix4.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.