You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Ilya Leviev (JIRA)" <ji...@apache.org> on 2007/06/05 14:25:26 UTC
[jira] Created: (HARMONY-4045) [drlvm][classloader][tc]Known/proven
race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at
find function
[drlvm][classloader][tc]Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function
-----------------------------------------------------------------------------------------------------------------------------
Key: HARMONY-4045
URL: https://issues.apache.org/jira/browse/HARMONY-4045
Project: Harmony
Issue Type: Bug
Components: DRLVM
Reporter: Ilya Leviev
Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function.
TC report on thread unsafe access that result in race conditions that occur during execution of find function.
Data-races:
Memory write at "method_lookup.cpp":241 conflicts with a prior memory read at "method_lookup.cpp":241
#ifdef VM_STATS
241 VM_Statistics::get_vm_stats().num_method_lookup_cache_miss++;
#endif //VM_STATS
As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I have marked it by special API for prevention of further alarms on this race.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4045) [drlvm][classloader][tc]Known/proven
race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at
find function
Posted by "Ilya Leviev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Leviev updated HARMONY-4045:
---------------------------------
Attachment: HARMONY-4045_add_markup.patch
> [drlvm][classloader][tc]Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-4045
> URL: https://issues.apache.org/jira/browse/HARMONY-4045
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Ilya Leviev
> Attachments: HARMONY-4045_add_markup.patch
>
>
> Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function.
> TC report on thread unsafe access that result in race conditions that occur during execution of find function.
> Data-races:
> Memory write at "method_lookup.cpp":241 conflicts with a prior memory read at "method_lookup.cpp":241
> #ifdef VM_STATS
> 241 VM_Statistics::get_vm_stats().num_method_lookup_cache_miss++;
> #endif //VM_STATS
> As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I have marked it by special API for prevention of further alarms on this race.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (HARMONY-4045) [drlvm][classloader][tc]Known/proven
race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at
find function
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky closed HARMONY-4045.
--------------------------------------
No response, assuming ok.
> [drlvm][classloader][tc]Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-4045
> URL: https://issues.apache.org/jira/browse/HARMONY-4045
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Ilya Leviev
> Assignee: Gregory Shimansky
> Attachments: HARMONY-4045_add_markup.patch
>
>
> Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function.
> TC report on thread unsafe access that result in race conditions that occur during execution of find function.
> Data-races:
> Memory write at "method_lookup.cpp":241 conflicts with a prior memory read at "method_lookup.cpp":241
> #ifdef VM_STATS
> 241 VM_Statistics::get_vm_stats().num_method_lookup_cache_miss++;
> #endif //VM_STATS
> As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I have marked it by special API for prevention of further alarms on this race.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-4045)
[drlvm][classloader][tc]Known/proven race conditions markup at
vm\vmcore\src\class_support\method_lookup.cpp at find function
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky resolved HARMONY-4045.
----------------------------------------
Resolution: Fixed
Patch applied at 544513.
> [drlvm][classloader][tc]Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-4045
> URL: https://issues.apache.org/jira/browse/HARMONY-4045
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Ilya Leviev
> Assignee: Gregory Shimansky
> Attachments: HARMONY-4045_add_markup.patch
>
>
> Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function.
> TC report on thread unsafe access that result in race conditions that occur during execution of find function.
> Data-races:
> Memory write at "method_lookup.cpp":241 conflicts with a prior memory read at "method_lookup.cpp":241
> #ifdef VM_STATS
> 241 VM_Statistics::get_vm_stats().num_method_lookup_cache_miss++;
> #endif //VM_STATS
> As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I have marked it by special API for prevention of further alarms on this race.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-4045)
[drlvm][classloader][tc]Known/proven race conditions markup at
vm\vmcore\src\class_support\method_lookup.cpp at find function
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky reassigned HARMONY-4045:
------------------------------------------
Assignee: Gregory Shimansky
> [drlvm][classloader][tc]Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-4045
> URL: https://issues.apache.org/jira/browse/HARMONY-4045
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Ilya Leviev
> Assignee: Gregory Shimansky
> Attachments: HARMONY-4045_add_markup.patch
>
>
> Known/proven race conditions markup at vm\vmcore\src\class_support\method_lookup.cpp at find function.
> TC report on thread unsafe access that result in race conditions that occur during execution of find function.
> Data-races:
> Memory write at "method_lookup.cpp":241 conflicts with a prior memory read at "method_lookup.cpp":241
> #ifdef VM_STATS
> 241 VM_Statistics::get_vm_stats().num_method_lookup_cache_miss++;
> #endif //VM_STATS
> As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I have marked it by special API for prevention of further alarms on this race.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.