DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:to:message-id:subject
	:mime-version:content-type:content-transfer-encoding:references;
	 q=dns; s=default; b=nVpUSdqXdoyzHxh88X/NrRzIpfoEZ9DryqGqsn8Dh7d
	nvf0t4kaKVPJHxCi98kt9nPov1Lfo9omozRigUrtbDNUcXWhxBbKJZ1zISmVoNzL
	OUAEl1bgjbthu8WhrfxqJm+VdFCc82wUvSXDvVLNBl/NbiKCUqMY9hRKaEvlAH6Q
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 3 Apr 2018 23:42:45 +0000 (UTC)
From: "Ilguiz Latypov via cygwin" <cygwin@cygwin.com>
Reply-To: Ilguiz Latypov <ilatypov@yahoo.ca>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Message-ID: <1342436895.1365392.1522798965341@mail.yahoo.com>
Subject: accept: Bad address
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <1342436895.1365392.1522798965341.ref@mail.yahoo.com>

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().

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

--
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