[Live-devel] live555 event trigger behaviour

[Ross Finlayson]

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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20120617/ae888c0a/attachment.html>