Matthias, Thanks for the note. You've correctly identified a potential race condition caused by "triggerEvent()" being called by a non-LIVE555 thread. I've now installed a new version (2012.06.17) that should avoid this problem. The solution was to no longer have the "triggerEvent()" function (the only function that can be called from a non-LIVE555 thread) access (read or write) the "fLastUsedTriggerMask" or "fLastUsedTriggerNum" variables. (The function still accesses (writes) the "fTriggeredEventClientDatas" and "fTriggersAwaitHandling" variables, but not in a way that can cause a race condition. (This is assuming, of course, that different threads never call "triggerEvent()" with the same "eventTriggerId").)
Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
