DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=ixIdAmIrcLaLNL9M
	xbvINTpykJ+jlraROGJAoqJsuxbdcB4Ye+TliIHTB7LNsHDMnNOXWLLBcNhRRSje
	BqV7SEUOCZoQlwc7LiEcgdTsHlclqSxkQ32KnVLyS+UzJxjfLMlJ2Mj7+eHNIgwQ
	FKIOlbT3wyOqBaaM8VBzivJAe54=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: accept: Bad address
To: cygwin@cygwin.com
References: <1342436895.1365392.1522798965341.ref@mail.yahoo.com> <1342436895.1365392.1522798965341@mail.yahoo.com>
From: Mark Geisert <mark@maxrnd.com>
Message-ID: <641856e3-338d-72b7-194b-da6073bf2c5f@maxrnd.com>
Date: Tue, 3 Apr 2018 22:59:31 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
MIME-Version: 1.0
In-Reply-To: <1342436895.1365392.1522798965341@mail.yahoo.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Ilguiz Latypov via cygwin wrote:
> Hello,
>
> The latest Cygwin 64-bit release with the snapshot cygwin1.dll copied on top of it shows an "accept: Bad address error" in 3 reproducible cases:
>
> (a) The sshd daemon on receiving a connection request.
> (b) The XWin server on receiving a connection request from an X11 client such as xterm.
> (c) The Python server receiving a TCP connection in the socket's accept().

That is likely a different problem with similar symptoms.

> A StackOverflow question 41018644 from December 2016 showed an example of the bug with the Python server (c).

There seems to have been a brief period of time in March where accept() was not 
working properly.  There was one report on the list (from Denis Excoffier) and 
at the same time it wasn't working for me, also using X, on a personal build of 
the Cygwin DLL from git source.  Denis later reported it working again, and I 
can confirm it is working again for me.

One option is to use the previous snapshot, dated 20180220.  The other is to 
wait until the next snapshot (after 20180309) is available.

Corinna or somebody else with the chops/access, could we get a new Cygwin DLL 
snapshot built when you have a chance?
Thanks,

..mark


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple