[jira] Resolved: (HARMONY-3959) [drlvm][exception] Known/proven race conditions markup at vm\vmcore\src\exception\exceptions_jit.cpp at exn_propagate_exception() function

["Gregory Shimansky (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HARMONY-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky resolved HARMONY-3959.
----------------------------------------

    Resolution: Fixed

Patch applied at 542203. Please check that it was applied as expected.

> [drlvm][exception] Known/proven race conditions markup at vm\vmcore\src\exception\exceptions_jit.cpp at exn_propagate_exception() function
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3959
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3959
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Ilya Leviev
>            Assignee: Gregory Shimansky
>         Attachments: HARMONY-3959_add_markup.patch
>
>
> Known/proven race conditions markup at vm\vmcore\src\exception\exceptions_jit.cpp at exn_propagate_exception() function
> TC report on thread unsafe access that result in race conditions that occur during execution of exn_propagate_exception (241).
> Write -> Write data-race:
> Memory write at "exceptions_jit.cpp":241 conflicts with a prior memory write at "exceptions_jit.cpp":241
>  239	#ifdef VM_STATS
>  240 	    exn_class->class_thrown();
>  241	    VM_Statistics::get_vm_stats().num_exceptions++;
> 	#endif // VM_STATS
> As issues 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.