* accept: Bad address [not found] <1342436895.1365392.1522798965341.ref@mail.yahoo.com> @ 2018-04-03 23:42 ` Ilguiz Latypov via cygwin 2018-04-04 5:59 ` Mark Geisert 0 siblings, 1 reply; 5+ messages in thread From: Ilguiz Latypov via cygwin @ 2018-04-03 23:42 UTC (permalink / raw) To: cygwin 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: accept: Bad address 2018-04-03 23:42 ` accept: Bad address Ilguiz Latypov via cygwin @ 2018-04-04 5:59 ` Mark Geisert 2018-04-04 6:36 ` Mark Geisert 2018-04-04 9:25 ` Corinna Vinschen 0 siblings, 2 replies; 5+ messages in thread From: Mark Geisert @ 2018-04-04 5:59 UTC (permalink / raw) To: cygwin 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: accept: Bad address 2018-04-04 5:59 ` Mark Geisert @ 2018-04-04 6:36 ` Mark Geisert 2018-04-04 9:25 ` Corinna Vinschen 1 sibling, 0 replies; 5+ messages in thread From: Mark Geisert @ 2018-04-04 6:36 UTC (permalink / raw) To: cygwin Mark Geisert, correcting my previous post: Mark Geisert wrote: > 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(). [...] > >> A StackOverflow question 41018644 from December 2016 showed an example of the >> bug with the Python server (c). That last report is likely a different problem with similar symptoms. > > There seems to have been a brief period of time in March where accept() was not > working properly. ^ in snapshots and Cygwin DLL built from source. Released Cygwin DLLs were not affected. > 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. Another option is to build your own Cygwin DLL from git source. > Corinna or somebody else with the chops/access, could we get a new Cygwin DLL > snapshot built when you have a chance? > Thanks, Sorry for the deficient description in my earlier post. ..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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: accept: Bad address 2018-04-04 5:59 ` Mark Geisert 2018-04-04 6:36 ` Mark Geisert @ 2018-04-04 9:25 ` Corinna Vinschen 2018-04-05 0:52 ` Ilguiz Latypov via cygwin 1 sibling, 1 reply; 5+ messages in thread From: Corinna Vinschen @ 2018-04-04 9:25 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 1582 bytes --] On Apr 3 22:59, Mark Geisert wrote: > 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. I reshuffled lots of socket code to make room for a new AF_UNIX implementation. While at it, I screwed up in a few places, so socket code was broken for a bit. The OpenSSH testsuite helped a lot to find the bugs, btw :} > Corinna or somebody else with the chops/access, could we get a new Cygwin > DLL snapshot built when you have a chance? New snapshots are up. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: accept: Bad address 2018-04-04 9:25 ` Corinna Vinschen @ 2018-04-05 0:52 ` Ilguiz Latypov via cygwin 0 siblings, 0 replies; 5+ messages in thread From: Ilguiz Latypov via cygwin @ 2018-04-05 0:52 UTC (permalink / raw) To: cygwin On Wed, Apr 04, 2018 at 11:25:30AM +0200, Corinna Vinschen wrote: > I reshuffled lots of socket code to make room for a new AF_UNIX > implementation. While at it, I screwed up in a few places, so > socket code was broken for a bit. The OpenSSH testsuite helped > a lot to find the bugs, btw :} > > > Corinna or somebody else with the chops/access, could we get a new Cygwin > > DLL snapshot built when you have a chance? > > New snapshots are up. Thanks, it worked. -- 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-04-05 0:52 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <1342436895.1365392.1522798965341.ref@mail.yahoo.com> 2018-04-03 23:42 ` accept: Bad address Ilguiz Latypov via cygwin 2018-04-04 5:59 ` Mark Geisert 2018-04-04 6:36 ` Mark Geisert 2018-04-04 9:25 ` Corinna Vinschen 2018-04-05 0:52 ` Ilguiz Latypov via cygwin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).