From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: recv() timeout problem
Date: Fri, 05 Jul 2013 13:11:00 -0000 [thread overview]
Message-ID: <20130705131151.GC12869@calimero.vinschen.de> (raw)
In-Reply-To: <51D6BF0B.5030002@tiscali.co.uk>
On Jul 5 13:41, David Stacey wrote:
> On 05/07/13 10:00, Corinna Vinschen wrote:
> >On Jul 4 19:34, David Stacey wrote:
> >>>Please find attached a short programme that demonstrates a problem
> >>>I'm having with recv() timeouts. Under Fedora 19 x64, the test
> >>>programme times out after three seconds (which is the desired
> >>>behaviour). However, when run from Cygwin, the call to recv() never
> >>>exits.
> >>>
> >>>I am using the latest snapshot (2013-07-03) in 32-bit Cygwin. OS is
> >>>Windows 7 Ultimate x64 SP1.
> >>>
> >>>Many thanks in advance for your help,
> >Unfortunately that won't work at the moment.
> >
> >The underlying implementation of recv is nonblocking. A blocking
> >Windows recv call is noninterruptible, unfortunately (at least up to
> >Windows 2003), so this was necessary to handle signals or
> >thread-cancellation.
> >
> >Due to its nonblocking nature under the hood, this doesn't support
> >SO_RCVTIMEO and SO_SNDTIMEO and, surprisingly, we never had a complaint
> >about that, despite its age.
> >
> >I can't promise a quick solution, but I put implementing handling of
> >SO_RCVTIMEO and SO_SNDTIMEO in recv/send on my TODO list. Of course,
> >patches are welcome, too.
> >
> >For the time being, I suggest to use select or poll with timeout
> >instead.
>
> Thank you for your e-mail, and for replying so quickly. Regarding
> the recv() timeouts: no problem, it's easy enough to work around. On
> your TODO list, file this one under things to do when you've finally
> got that cat.
LOL. Nah, it's an interesting little problem, I'm pretty sure I'll
have a look later this month.
> I think that's the last of my Poco problems out of the way. I'll
> give it a clean build and test, and send an ITP either this evening
> or tomorrow.
>
> Thanks once again for your help,
No worries. And thanks for the testcase, I'm sure I'll use it to test
the SO_RCVTIMEO implementation when I get to it.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
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
prev parent reply other threads:[~2013-07-05 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 18:34 David Stacey
2013-07-05 9:00 ` Corinna Vinschen
2013-07-05 12:42 ` David Stacey
2013-07-05 13:11 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130705131151.GC12869@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).