From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124243 invoked by alias); 4 Apr 2018 05:59:38 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 124235 invoked by uid 89); 4 Apr 2018 05:59:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=symptoms, H*Ad:U*mark, denis, personal X-HELO: m0.truegem.net Received: from m0.truegem.net (HELO m0.truegem.net) (69.55.228.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 04 Apr 2018 05:59:35 +0000 Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id w345xXXJ009231 for ; Tue, 3 Apr 2018 22:59:33 -0700 (PDT) (envelope-from mark@maxrnd.com) Received: from 76-217-5-154.lightspeed.irvnca.sbcglobal.net(76.217.5.154), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdKIMwg2; Tue Apr 3 22:59:32 2018 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 Message-ID: <641856e3-338d-72b7-194b-da6073bf2c5f@maxrnd.com> Date: Wed, 04 Apr 2018 05:59:00 -0000 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 X-SW-Source: 2018-04/txt/msg00017.txt.bz2 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