On May 26 12:08, Sunil wrote:
> this issue is not fixed in any later snapshots, not
> even the just released 1.5.17.
>
> can someone with the knowledge of cygwin socket code
> comment on it please?
>
> Thanks,
> Sunil
>
> --- "Gerrit P. Haase" <[EMAIL PROTECTED]> wrote:
> > Sunil wrote:
> >
> > > This piece of code hangs with cygwin1.dll >=1.5.15
> > > during connect(), strace is attached. The same
> > code
> > > runs fine with cygwin1.dll version 1.5.13.
> > >
> > > --------------------------------
> > > fd = socket (proto->family, 1,
> > > proto->stream_proto_num);
> > >
> > > if (fd < 0) {
> > > ;
> > > goto out;
> > > }
> > >
> > > if (options & LINK_CONNECTION_NONBLOCKING) {
> > > # 553 "linc-connection.c"
> > > if (fcntl (fd, 4, 0x4000) < 0)
> > > goto out;
> > >
> > > }
> > >
> > > if (fcntl (fd, 2, 1) < 0)
> > > goto out;
> > >
> > > { long int __result; do __result = (long int)
> > > (connect (fd, saddr, saddr_len)); while (__result
> > ==
> > > -1L && (*__errno()) == 4); rv = __result; };
> > > # 596 "linc-connection.c"
> > > if (rv && (*__errno()) != 119)
> > > goto out;
> > >
> > > ---------------------------
Can you please create a simple(!), short(!), stand-alone(!) testcase which
builds OOTB(!) and uses the symbolic constants rather than numeric constants?
Numbers as 4, 0x4000, 2, 1 in the context of fcntl don't make any sense at
all. Neither does a socket(2) call with variables set to some unknown value.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
