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
X-WM-Posted-At:	avacado.atomice.net; Sat, 13 Apr 02 18:23:19 +0100
Message-ID:	<011b01c1e30f$e7f740c0$0100a8c0@advent02>
From:	"Chris January" <chris AT atomice DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<15561 DOT 26590 DOT 782158 DOT 717023 AT lineone DOT net> <20020413163354 DOT GA7284 AT redhat DOT com>
Subject:	Re: gettime time travels after suspend
Date:	Sat, 13 Apr 2002 18:23:19 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

> >I have a running process which prints out the result of gettimeofday()
> >at regular intervals. If I suspend and resume my machine then the
> >value returned by gettimeofday() is incorrect - it jumps several days
> >into the future. Doing the same with time() is fine.
> >
> >I don't want to point fingers, but I suspect the following 1.3.10
> >change:
> > - Use QueryPerformance* functions for gettimeofday calls. (cgf)
>
> Patches gratefully accepted.
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?

Chris



--
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 -