Re: accept: Bad address

2018-04-04 Thread Ilguiz Latypov via 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 :} >

Re: accept: Bad address

2018-04-04 Thread Corinna Vinschen
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: > > > &

Re: accept: Bad address

2018-04-04 Thread Mark Geisert
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

Re: accept: Bad address

2018-04-04 Thread Mark Geisert
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 connecti

accept: Bad address

2018-04-03 Thread Ilguiz Latypov via 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