Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Message-ID:	<3E68C96A.3B85E100@ieee.org>
Date:	Fri, 07 Mar 2003 11:31:38 -0500
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
X-Accept-Language:	en,pdf
MIME-Version:	1.0
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: [Fwd: Re: exim fclose() warning message (was Re: 1.3.21)]
References:	<3E68B63E DOT CC299937 AT ieee DOT org> <20030307161803 DOT GA1193 AT cygbert DOT vinschen DOT de>

Corinna Vinschen wrote:

> >   185   94896 [main] sc11 2676 __set_winsock_errno: fixup_before_fork_exec:328 - winsock error 10022 -> errno 22
> 
> Invalid argument?!?  Why invalid argument?

<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/winsock/windows_sockets_error_codes_2.asp>
Invalid argument. 
Some invalid argument was supplied (for example, specifying an invalid level
to the setsockopt function). In some instances, it also refers to the current
state of the socket—for instance, calling accept on a socket that is not listening. 

It's probably the "state of the socket" clause, probably due to something
inherited.

Pierre

- Raw text -