Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.protocols.tcp-ip    |    TCP and IP network protocols.    |    14,669 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 13,930 of 14,669    |
|    Les Cargill to All    |
|    send() crash    |
|    14 Feb 13 12:24:41    |
      From: lcargill99@comcast.com              I am writing a TCP server. It is running on an       embedded linux platform, not a workstation. Yes,       I have full source to the kernel and all drivers.              If the following sequence occurs, send()crashes without       returning:              Client Server       send()        select()        recv()       close()        send() *crashes*              I somehow don't think it is supposed to do that.              How can I tell the socket is closed before calling send()?              please spare the assembled any "but it's not supposed to do that".       It does; it's likely a bug and not one I will spend any       time chasing if I can find a workaround.              Thanks in advance.              --       Les Cargill              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca