Ross Finlayson wrote:
That doesn't matter, because *TCP* packets will still be arriving (on
the TCP socket), and will be handled. This is a Red Herring.
No, that TCP socket has been closed - and the corresponding socket ID
refers occasionally to an UDP socket within the same call to SingleStep
- if it was a red herring the TaskScheduler was not going to be stuck.
That's a fact, not an argument. I have debugged a real problem, not
imagined one.
Look - I do not want you change the code because of my custom code! just
hoped to be of some help pointing out a problem that have let me become
mad! It seems to me you have not got the point.
Nevermind. I know how to deal with it.
Regards,
Sigismondo
--
------------------------------------------------------------------
Sigismondo Boschi, PhD TotalWire S.r.l.
[EMAIL PROTECTED] http://www.totalwire.it
cell: +39 346 7911896 tel: +39 051 302696
begin:vcard
fn:Sigismondo Boschi
n:Boschi;Sigismondo
org:TotalWire
adr:;;via Valdossola, 25/b;Bologna;BO;40134;Italy
email;internet:[EMAIL PROTECTED]
tel;work:+39 051 302696
tel;cell:+39 346 7911896
x-mozilla-html:FALSE
url:http://www.totalwire.it
version:2.1
end:vcard
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
