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/01 15:16:16 UTC
[jira] Created: (HARMONY-4027) [drlvm][object][tc]Known/proven race
conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at
vm_anewarray_resolved_array_type function.
[drlvm][object][tc]Known/proven race conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
-------------------------------------------------------------------------------------------------------------------------------------------
Key: HARMONY-4027
URL: https://issues.apache.org/jira/browse/HARMONY-4027
Project: Harmony
Issue Type: Bug
Components: DRLVM
Reporter: Ilya Leviev
Known/proven race condition markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
TC report on thread unsafe access that result in race conditions that occur during execution of vm_anewarray_resolved_array_type function.
Data-races:
Memory read at "vm_arrays.cpp":67 conflicts with a prior memory write at "vm_arrays.cpp":67
As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I mark 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-4027) [drlvm][object][tc]Known/proven race
conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at
vm_anewarray_resolved_array_type function.
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky closed HARMONY-4027.
--------------------------------------
No response, assuming ok.
> [drlvm][object][tc]Known/proven race conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-4027
> URL: https://issues.apache.org/jira/browse/HARMONY-4027
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Ilya Leviev
> Assignee: Gregory Shimansky
> Attachments: HARMONY-4027_add_markup.patch
>
>
> Known/proven race condition markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> TC report on thread unsafe access that result in race conditions that occur during execution of vm_anewarray_resolved_array_type function.
> Data-races:
> Memory read at "vm_arrays.cpp":67 conflicts with a prior memory write at "vm_arrays.cpp":67
> As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I mark 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-4027) [drlvm][object][tc]Known/proven
race conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at
vm_anewarray_resolved_array_type function.
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky reassigned HARMONY-4027:
------------------------------------------
Assignee: Gregory Shimansky
> [drlvm][object][tc]Known/proven race conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-4027
> URL: https://issues.apache.org/jira/browse/HARMONY-4027
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Ilya Leviev
> Assignee: Gregory Shimansky
> Attachments: HARMONY-4027_add_markup.patch
>
>
> Known/proven race condition markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> TC report on thread unsafe access that result in race conditions that occur during execution of vm_anewarray_resolved_array_type function.
> Data-races:
> Memory read at "vm_arrays.cpp":67 conflicts with a prior memory write at "vm_arrays.cpp":67
> As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I mark 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-4027) [drlvm][object][tc]Known/proven race
conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at
vm_anewarray_resolved_array_type function.
Posted by "Ilya Leviev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Leviev updated HARMONY-4027:
---------------------------------
Attachment: HARMONY-4027_add_markup.patch
> [drlvm][object][tc]Known/proven race conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-4027
> URL: https://issues.apache.org/jira/browse/HARMONY-4027
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Ilya Leviev
> Attachments: HARMONY-4027_add_markup.patch
>
>
> Known/proven race condition markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> TC report on thread unsafe access that result in race conditions that occur during execution of vm_anewarray_resolved_array_type function.
> Data-races:
> Memory read at "vm_arrays.cpp":67 conflicts with a prior memory write at "vm_arrays.cpp":67
> As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I mark 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-4027) [drlvm][object][tc]Known/proven
race conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at
vm_anewarray_resolved_array_type function.
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky resolved HARMONY-4027.
----------------------------------------
Resolution: Fixed
Patch applied at 544511.
> [drlvm][object][tc]Known/proven race conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-4027
> URL: https://issues.apache.org/jira/browse/HARMONY-4027
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Ilya Leviev
> Assignee: Gregory Shimansky
> Attachments: HARMONY-4027_add_markup.patch
>
>
> Known/proven race condition markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> TC report on thread unsafe access that result in race conditions that occur during execution of vm_anewarray_resolved_array_type function.
> Data-races:
> Memory read at "vm_arrays.cpp":67 conflicts with a prior memory write at "vm_arrays.cpp":67
> As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I mark 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.