You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Gregory Shimansky (JIRA)" <ji...@apache.org> on 2007/01/24 12:53:50 UTC
[jira] Commented: (HARMONY-3002) [drlvm] Race condition in leads to
VM crash on SMP systems on HARMONY-2386
[ https://issues.apache.org/jira/browse/HARMONY-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467007 ]
Gregory Shimansky commented on HARMONY-3002:
--------------------------------------------
I've reproduced the crash in 2 different places, but the problem in both cases seems to be an absent write barrier somewhere in lock reservation/unreservation code.
> [drlvm] Race condition in leads to VM crash on SMP systems on HARMONY-2386
> --------------------------------------------------------------------------
>
> Key: HARMONY-3002
> URL: https://issues.apache.org/jira/browse/HARMONY-3002
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Linux ia32, windows ia32
> Reporter: Gregory Shimansky
>
> I am not sure this is a class loader bug, but the crash happens on class loader code in class_initialize. When running the test in HARMONY-2386 many times in a loop it crashes after some time. The fat monitor which is used for synchronization in Class::initialize appears to be uninitialized or corrupted. It could be a thread manager bug or enumeration problem as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.