Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Subject:	RE: gettime time travels after suspend
Date:	Sun, 14 Apr 2002 14:35:17 +1000
MIME-Version:	1.0
Message-ID:	<FC169E059D1A0442A04C40F86D9BA7600C5E35@itdomain003.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
content-class:	urn:content-classes:message
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Chris January" <chris AT atomice DOT net>, <cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g3E4ZbX04951

> -----Original Message-----
> From: Chris January [mailto:chris AT atomice DOT net] 

> There is a similar problem here with timeouts passed to 
> WaitForSingleObjectEx, and WaitForMultipleObjectsEx. I was 
> thinking of generating a patch that does a single retry when 
> a Wait* times out. Is the consensus that this would be useful or not?

I think it depends on *where* the Wait* function is called. In various
pthread calls for instance, we should not retry - because the timeouts
are passed in as absolute values, not as elapsed values.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -