[rtmpdump] Wrong socket timeout in MinGW version
Skaarj NaPali
skaarj1 at gmail.com
Fri Jan 1 16:01:04 CET 2010
Hi,
The MinGW version has a problem with the TCP/IP socket timeout which
is applied in "bool RTMP_Connect(RTMP * r)". The Winsock support for
"SO_RCVTIMEO" does not use the "struct timeval" but is using an
integer instead which specifies the timeout in milliseconds. So, the
current MinGW version of rtmpdump tends to throw a socket error (10060
– WSAETIMEDOUT) because it treats the 'seconds' which are specified in
"Link.timeout" and which are passed in "tv.tv_sec" actually as
'milliseconds'.
The attached patch shows a possible way to fix it for MinGW.
KR
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mingw_SO_RCVTIMEO.patch
Type: application/octet-stream
Size: 879 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/rtmpdump/attachments/20100101/5bb2abab/attachment.obj>
More information about the rtmpdump
mailing list