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: <01f801c243da$1290db90$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: <cygwin-developers AT cygwin DOT com>
References: <015e01c243ce$8390e3f0$6132bc3e AT BABEL>
Subject: Re: getsockname / recvfrom bug (?)
Date: Wed, 14 Aug 2002 22:32:20 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

"Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com> wrote:
> Having changed the socket code to use recvfrom, I've now found
an
> apparent bug whereby recvfrom will fail with WSAEINVAL.
[snip]
> Anyhow the problem occurs if you dup(2) a socket and then
operate
> on the duplicate copy w/o closing the original socket and
without
> forking.
[snip]

As it turns out, it's nothing like that simple, as I've got
another program doing the "same" thing that works fine.  It'll
probably turn out to be something unrelated that I've broken in
one of my test programs.  Next time I'll try to report back when
I've got something *interesting* to report :-(

// Conrad