X-Recipient: archive-cygwin AT delorie DOT com 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 = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=uEbDqdEnhW/DU0yqCSvAx74VA6w=; b=ok7QL13utfouoXP9m 9GDv+OLU4l2Ex1Raw9jm3Vk0GRcH4ew7w57hEKUrTsOFDQeWocrLp+Bl8c1VcqOF kqKSvUPIoJpgRziJH+doR2XVVNDjepAA2vVbI5jwXcuOpAcw/L+DvV3kulitmLvR E4ZG4vfIfZnMJuixj1dBUbsCLI= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*x:5.0, H*x:Windows, H*x:WebService, H*x:Mozilla X-HELO: sonic307-12.consmr.mail.ne1.yahoo.com Date: Tue, 3 Apr 2018 23:42:45 +0000 (UTC) From: "Ilguiz Latypov via cygwin" Reply-To: Ilguiz Latypov To: "cygwin AT cygwin DOT 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 DOT 1365392 DOT 1522798965341 DOT ref AT mail DOT yahoo DOT 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