> Having thought about it some more, I don't think it's enough to just protect
> calls to triggerEvent() because 'fTriggersAwaitingHandling' is still modified
> by BasicTaskScheduler::SingleStep().
The intention of the code that implements “BasicTaskScheduler” was that:
1/ The event loop code (which is always just a single thread, remember) does
nothing with “fTriggersAwaitingHandling” except clear (using “&=~”) a single
bit that was already set, and
2/ The other thread(s) that can trigger event(s) do nothing with
“fTriggersAwaitingHandling” except set (using “|=“) bit(s) that were not
already set.
If these two conditions are met, *and* if the ‘clear a bit’ and ‘set a bit’
operations are atomic, then the code will be thread-safe.
(If, OTOH, you’re worried that the ‘clear a bit’ and ‘set a bit’ operations
might not be atomic on your system, then you’d need to write your own
“TaskScheduler” subclass instead.)
Looking at the code again just now, however, I realized that the event loop
code does not always satisfy condition 1/. Line 183 of
“BasicTaskScheduler.cpp” should be changed from:
fTriggersAwaitingHandling = 0;
to
fTriggersAwaitingHandling &=~ fLastUsedTriggerMask;
I have just released a new version (2015.03.16) of the code that fixes this.
You should upgrade to this version.
You should also make sure that your own code satisfies condition 2/. I.e., you
should make sure that your code is never calling “triggerEvent()” more than
once with the same ‘event trigger’ value, unless you’re sure that the first
event (for that event trigger) has already been handled. (In particular, you
should never call “triggerEvent()” with the same ‘event trigger’ value from
more than one thread.)
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
