X-Spam-Check-By: sourceware.org Date: Tue, 13 Feb 2007 11:52:37 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: pthread_cond_timedwait Message-ID: <20070213105237.GP4158@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <41FCF2210BBCFA4BA3EF3B810C19E4D028C5F3 AT kda-beexc-01 DOT kda DOT kongsberg DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41FCF2210BBCFA4BA3EF3B810C19E4D028C5F3@kda-beexc-01.kda.kongsberg.com> User-Agent: Mutt/1.4.2.2i 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 Feb 12 12:10, Ingvill DOT Grefstad AT kongsberg DOT com wrote: > Hi, > I have tried to use the pthread_cond_timedwait, but it doesn't seem to > work properly. > > It returns immediately with a return value of 116 (ETIMEDOUT) even if I > set the timeout period to e.g. 10 seconds. > > I have locked the mutex and initialized the condition variable before > the invokation is made. > > What is wrong? cockpit error, maybe. The timeval value given to pthread_cond_timedwait is supposed to be an absolute timestamp, not a relative timeout. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/