<div dir="ltr"><div>in RTSPClient destructor the same "socket num" (fInputSocketNum)
must be used when clearing "server request alternative byte handler" <br>as when setting the handler, but this socket num fInputSocketNum is "cleared" in resetTCPSockets and in grabSocket,<br></div>so
if after setting the "server request alternative byte handler"
resetTCPSockets or grabSocket is called and then the RTSPClient is
deleted the handler is not cleared <br>which then contains pointer to the deleted RTSPClient<br><div><br></div><div>best regards<br></div>gerald<br><br><br><div class="gmail_extra"><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername"></b> <span dir="ltr"><<a href="mailto:live-devel-request@ns.live555.com" target="_blank">live-devel-request@ns.live555<wbr>.com</a>></span><br>Date: Wed, May 10, 2017 at 9:00 PM<br>Subject: live-devel Digest, Vol 162, Issue 9<br>To: <a href="mailto:live-devel@ns.live555.com" target="_blank">live-devel@ns.live555.com</a><br><br><br>Send live-devel mailing list submissions to<br>
<a href="mailto:live-devel@lists.live555.com" target="_blank">live-devel@lists.live555.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" rel="noreferrer" target="_blank">http://lists.live555.com/mailm<wbr>an/listinfo/live-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:live-devel-request@lists.live555.com" target="_blank">live-devel-request@lists.live5<wbr>55.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:live-devel-owner@lists.live555.com" target="_blank">live-devel-owner@lists.live555<wbr>.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of live-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: segfault RtspClient (Ross Finlayson)<br>
2. Re: segfault RtspClient (Ross Finlayson)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Tue, 9 May 2017 12:04:48 -0700<br>
From: Ross Finlayson <<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>><br>
To: LIVE555 Streaming Media - development & use<br>
<<a href="mailto:live-devel@ns.live555.com" target="_blank">live-devel@ns.live555.com</a>><br>
Subject: Re: [Live-devel] segfault RtspClient<br>
Message-ID: <<a href="mailto:0EAA9CFB-4D90-4550-A3E0-48BFCF2C8C67@live555.com" target="_blank">0EAA9CFB-4D90-4550-A3E0-48BFC<wbr>F2C8C67@live555.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
> in previous version in RtspClient::resetTCPSockets the "alternative byte handler" is cleared using the "input socket num" before setting it to -1.<br>
><br>
> RTPInterface::clearServerReque<wbr>stAlternativeByteHandler(envir<wbr>(), fInputSocketNum); // in case we were receiving RTP-over-TCP<br>
><br>
> i think this line should be added again?<br>
<br>
I?m puzzled. That line *is* in the ?RTSPClient? destructor (see ?RtspClient.cpp?, line 400), and has been there for several years, I think.<br>
<br>
Are you sure you really have the latest version of the code? See <a href="http://live555.com/liveMedia/faq.html#latest-version" rel="noreferrer" target="_blank">http://live555.com/liveMedia/f<wbr>aq.html#latest-version</a><br>
<br>
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" rel="noreferrer" target="_blank">http://www.live555.com/</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 9 May 2017 12:25:21 -0700<br>
From: Ross Finlayson <<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>><br>
To: LIVE555 Streaming Media - development & use<br>
<<a href="mailto:live-devel@ns.live555.com" target="_blank">live-devel@ns.live555.com</a>><br>
Subject: Re: [Live-devel] segfault RtspClient<br>
Message-ID: <<a href="mailto:A080B9B8-6609-4ACA-83A4-DB99106F8B2F@live555.com" target="_blank">A080B9B8-6609-4ACA-83A4-DB991<wbr>06F8B2F@live555.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
> in previous version in RtspClient::resetTCPSockets the "alternative byte handler" is cleared using the "input socket num" before setting it to -1.<br>
><br>
> RTPInterface::clearServerRequ<wbr>estAlternativeByteHandler(envi<wbr>r(), fInputSocketNum); // in case we were receiving RTP-over-TCP<br>
><br>
> i think this line should be added again?<br>
<br>
OK, I think I understand now what you?re asking. The line you?re talking about is currently in the ?RTSPClient? destructor, but *not* in the ?resetTCPSockets()? function (which is called more often).<br>
<br>
I?ll take a closer look at the code, to see whether it should be put (back?) in ?resetTCPSockets()? instead. Stay tuned?<br>
<br>
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" rel="noreferrer" target="_blank">http://www.live555.com/</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com" target="_blank">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" rel="noreferrer" target="_blank">http://lists.live555.com/mailm<wbr>an/listinfo/live-devel</a><br>
<br>
<br>
------------------------------<br>
<br>
End of live-devel Digest, Vol 162, Issue 9<br>
******************************<wbr>************<br>
</div><br></div>
</blockquote></div><br></div></div>