X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=1.8 required=5.0 tests=AWL,BAYES_00,CHARSET_FARAWAY_HEADER X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 26 May 2010 16:02:45 +0300 Message-ID: Subject: Re: 1.7.5-1: problem with settimeofday() & gettimeofday() From: =?KOI8-R?B?/sXLIP7Fy8nT1A==?= <4ekuct@tut.by> To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com > Hello. It seems that I found a problem with settimeofday() and > gettimeofday() calls in a single context. The problem is that if we > set a new time with settimeofday() call it completes succefully and > system time is updated. But then if we try to get current time with > gettimeofday() call it returns old time! I've looked into 'times.cc' and found that 'hires_ms gtod' timer (which is used in gettimeofday()) is not reset with 'hires_ms::prime()' in settimeofday() after system call to Win32 API SetSystemTime() function! I think this is the reason of described behaviour. -- 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