Re: [Live-devel] windows winsock error 10038

2013-06-30 Thread Ross Finlayson
On Jun 29, 2013, at 11:40 PM, Andrey wrote: > Thank you, Ross. Error no longer occurs. That's great to hear. I've now installed a new version (2013.06.30) of the code that includes this fix. Ross Finlayson Live Networks, Inc. http://www.live555.com/ __

Re: [Live-devel] windows winsock error 10038

2013-06-29 Thread Andrey
Thank you, Ross. Error no longer occurs. 30.06.2013 2:20, Ross Finlayson ?: Andrey, Thanks again. I think (but am not yet 100% sure) that I've found and fixed the problem. Please replace your copy of "RTPInterface.cpp" with this one, and let me know (with debugging output) if you see t

Re: [Live-devel] windows winsock error 10038

2013-06-29 Thread Ross Finlayson
Andrey,Thanks again.  I think (but am not yet 100% sure) that I've found and fixed the problem.  Please replace your copy of "RTPInterface.cpp" with this one, and let me know (with debugging output) if you see the error again. Ross FinlaysonLive Networks, Inc.http://www.live555.com/ RTPInterface

Re: [Live-devel] windows winsock error 10038

2013-06-29 Thread Андрей
Hi, Ross. Here's a new debug log output: RTSPClientConnection[060F24E0]::RTSPClientConnection() socket 568 SocketDescriptor[01377DD0]::SocketDescriptor() socket 568 SocketDescriptor[01377DD0]::registerRTPInterface(channel 0): socket 568 SocketDescriptor[01377DD0]::tcpReadHandler1(): socket 568: r

Re: [Live-devel] windows winsock error 10038

2013-06-27 Thread Andrey
It is important to note that the error occurs on the socket fClientInputSocket and the socket when using the TCP, for UDP is not an issue. 27.06.2013 11:24, Andrey пишет: Hi, Ross. I was able to simulate error WINSOCK 10038. To do this, RTSP client must ask the server to send the stream. Ac

Re: [Live-devel] windows winsock error 10038

2013-06-27 Thread Andrey
Hi, Ross. I was able to simulate error WINSOCK 10038. To do this, RTSP client must ask the server to send the stream. Accordingly, you should set REQUEST_STREAMING_OVER_TCP to True. Then you need to properly shut down the client, without sending the command TEARDOWN. Maybe a few times. And the

Re: [Live-devel] windows winsock error 10038

2013-06-20 Thread Ross Finlayson
> Bellow is my app call stack This call stack tells me that you are *not* using the latest version of the code (because, in the latest version of the code, the "SocketDescriptor" object is deleted from "tcpReadHandler()", not from "tcpReadHandler1()". A bug in this code was fixed on April 30th

Re: [Live-devel] windows winsock error 10038

2013-06-20 Thread 谢永达
It's my fault, I forgot the class name, I checkout the code, class name is SocketDescriptor. Bellow is my app call stack , I don't know why its' deconstruct function has been call twice. #0 0x003c954328a5 in raise () from /lib64/libc.so.6 #1 0x003c95434085 in abort () from /lib64/libc.s

Re: [Live-devel] windows winsock error 10038

2013-06-19 Thread Ross Finlayson
> Hmmm, I found that the class "TCPSocketDescribe" in RTPInterface.cpp had been > double free sometimes That sounds good - except that our code doesn't have a class named "TCPSocketDescribe". If you find a specific bug in our code, however (be sure to use the latest version!), please let us kn

Re: [Live-devel] windows winsock error 10038

2013-06-19 Thread 谢永达
Hmmm, I found that the class "TCPSocketDescribe" in RTPInterface.cpp had been double free sometimes, when it happen, the app crash. 2013/6/18 Andrey > Thanks for the quick reply. However, the error occurs even if the test > code testOnDemandRTSPServer reuseFirstSource set to True. I have not >

Re: [Live-devel] windows winsock error 10038

2013-06-18 Thread Serge . Grondin
, Date: 2013-06-18 16:04 Subject: Re: [Live-devel] windows winsock error 10038 Sent by:live-devel-boun...@ns.live555.com The problem I found is in RTPInterface.cpp file -> SocketDescriptor::tcpReadHandler1 line 422 If readSocket fails (-1) it trig

Re: [Live-devel] windows winsock error 10038

2013-06-18 Thread Ross Finlayson
> The problem I found is in RTPInterface.cpp file > > -> SocketDescriptor::tcpReadHandler1 line 422 > If readSocket fails (-1) it triggers a deletion of the SocketDescriptor object > Correct. > > However this is leaving a dangling pointer in the HashTable in RTPInterface > (lookupSocketDescript

Re: [Live-devel] windows winsock error 10038

2013-06-18 Thread Serge . Grondin
From: Ross Finlayson To: LIVE555 Streaming Media - development & use , Date: 2013-06-18 04:18 Subject:Re: [Live-devel] windows winsock error 10038 Sent by:live-devel-boun...@ns.live555.com Thanks for the quick reply. However, the error occurs even

Re: [Live-devel] windows winsock error 10038

2013-06-18 Thread Ross Finlayson
> Thanks for the quick reply. However, the error occurs even if the test code > testOnDemandRTSPServer reuseFirstSource set to True. I have not changed > anything in the code, except the reuseFirstSource. If that's the case, then unfortunately you're going to have to track down the specific pro

Re: [Live-devel] windows winsock error 10038

2013-06-17 Thread Ross Finlayson
> After a call to select () the invalid socket error occurs. It occurs in > multiple-connected disabled client to the server, and the server will > eventually fall. I know that you can override internalError () function, but > it would still understand the cause of the error. The problem is tha