I’m really not interested in engaging in random speculation about this, because
(based on experience) that quickly becomes a ’rat hole’.
If you have definitive proof that there’s a race condition that’s causing your
problem, then I’m interested in hearing about it. But your problem might well
have some other cause.
For the record, here is the lone statement that updates
“fTriggersAwaitingHandling” in our implementation of “triggerEvent()” - the
only place where that variable can be updated by a non-LIVE555 thread:
fTriggersAwaitingHandling |= 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
