[zeromq-dev] Mac OS X: test_shutdown_stress sometimes fails

[Martin Lucina]

sustrik at 250bpm.com said:
> On 11/01/2010 08:19 PM, Christian Gudrian wrote:
> 
> > Invalid argument
> > nbytes != -1 (../../src/tcp_socket.cpp:197)
> 
> It's the return value from send(2) call, "Invalid argument" = EINVAL.
> 
> However, OSX reference doesn't mention EINVAL as valid error for send :(
> 
> http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man2/send.2.html
> 
> Anyone any idea why this may happen?

I can think of at least the case where the signaler has been destroyed but
something is still trying to use it.  That would result in a send() on a
file descriptor which has been close()d, which would presumably return
EINVAL.

POSIX does not seem to specify EINVAL as a valid return code from send(),
neither does FreeBSD on which the OSX network stack is based, but Linux
does list it rather vaguely as "Invalid argument passed".

-mato