Race condition in ACE_Future double checked locking pattern code about ace_tao HOT 6 CLOSED

We've fixed the race condition with following patch:
0001-Fixed-possible-data-race-in-ACE_Future-set-get.patch

The following code we used for testing:
acefuturetester.tar.gz

from ace_tao.

Please open a pull request with your patch add your test under ACE_wrappers/tests so that it is compiled/tested as part of our test suite

from ace_tao.

Maybe determine the max threads based on the number of cpu cores on the system and run it for some minutes, a run of 4 hours is to long for our test suite. Maybe split the PR in two, one with just the test extension, second with the fix

from ace_tao.

The test Future_Test.cpp will test this from functional point of view.
The issue can't be easily reproduced. It requires fast machines and it depends on the CPU and compiler being used.

from ace_tao.

I think it would be helpful to have the additional test be added to future_test but just do some interations and make it possible to control the amount of iterations on the commandline. What kind of CPU/compiler are required, some background information on why it happens only with some specific cpu/compiler would be helpful, it is very likely that we have more constructs like this

from ace_tao.

Looks similar to #2170

from ace_tao.