harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Leviev (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-3959) [drlvm][exception] Known/proven race conditions markup at vm\vmcore\src\exception\exceptions_jit.cpp at exn_propagate_exception() function
Date Thu, 24 May 2007 15:45:16 GMT
[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


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.


Mime
View raw message