Thanks. These will be fixed in the next release of the software.
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
> This is an educated guess.
Remember, You Have Complete Source Code. Rather than making "an educated
guess", you should be able to figure out exactly what's going on.
> In Cygwin the RTSPClientConnection
> socket doesn't close explicitly after a TEAR. The read bitmask
> in the call to select
On 2/25/2014 09:17, Warren Young wrote:
because it wants you to call recv() one last time and get -1, which is
how BSD sockets (and Winsock) signal that condition.
I meant 0, of course.
___
live-devel mailing list
live-devel@lists.live555.com
http://l
On 2/24/2014 06:36, MartÃnez Contador, Daniel [ELIMCO] (CA) wrote:
This is an educated guess. In Cygwin the RTSPClientConnection
socket doesn't close explicitly after a TEAR. The read bitmask
in the call to select in BasicTaskScheduler remains active
and the call returns immediately by some reas
Hello Ross,
I've run code analysis tool against the Live555 and found two suspicious
places, which might be an error:
Live555 from 2014/02/19
H264or5VideoStreamFramer.cpp, line 696 (681):
unsigned num_negative_pics = 0;
unsigned num_positive_pics = 0;
>>> for (unsigned j = 0; j < num_negati
