On Thu, Oct 24, 2013 at 9:15 PM, Ross Finlayson <finlay...@live555.com>wrote:
> Thanks for the clarifications, I've looked further and found that send() > is returning -1, with errno being set to EPIPE. The problem is in "select" > in BasicTaskScheduler::SingleStep still indicating a writable socket even > when it is disconnected. Is this a libc problem? > > > If "select()" is reporting that a socket is writable, when it's not, then > that would appear to be a bug... > > > I've found a reference on what would be the proper behavior, In Unix Network Programming, Volume 1: The Sockets Networking API (3rd Edition), it is noted that a socket will be ready for writing if the write half of the connection is closed, but a write will generate a SIGPIPE. So a check on EPIPE in the send call will be needed. Park.
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
