X-Spam-Check-By: sourceware.org Date: Mon, 12 Feb 2007 07:11:07 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: strange bug in gettimeofday function Message-ID: <20070212121107.GB8143@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1562006224 DOT 20070211192014 AT gnu DOT org> <45CFD856 DOT 10106 AT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45CFD856.10106@gmail.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, Feb 12, 2007 at 11:00:38AM +0800, Carlo Florendo wrote: >Andrew Makhorin wrote: >>Hi, >> >>I detected a strange bug in the standard function gettimeofday. >>It *sometimes* reports the time which being expressed as the integer >>number of milliseconds is *less* than the time obtained *earlier* with >>the same function. > >If you mean that you call gettimeofday twice and you get different >values at each call, with a difference of about 100 ms, then this is all >right. Read on... As the author of the function in question, I would still like to get a test case. -- 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/