public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Fu Limin" <limin.fu@ircc.it>
To: pthreads-win32@sources.redhat.com
Subject: Problem with pthread_cond_timedwait()
Date: Tue, 27 Sep 2005 11:13:00 -0000	[thread overview]
Message-ID: <1402.130.192.136.198.1127819578.squirrel@130.192.136.198> (raw)

Hello,

There is a strange problem with pthread_cond_timedwait() in my program
using pthread-win32, I found it doesn't
wait at all. Here is part of the codes,

    struct timespec timeout;
    timeout.tv_sec = time(NULL) + 10;
    timeout.tv_nsec = 0;

    pthread_cond_timedwait( & myCondVar, & mutex->myMutex, &timeout );

This part works as expected under linux. The compiler I used is gcc3.4.2,
and I used the pre-built pthread-win32, v2.7.
Am I using pthread_cond_timedwait() properly?

Another question, I saw in pthread documentations that the "timeout" is
prepare in the following way,

struct timeval now;
struct timespec timeout;

gettimeofday(&now);
timeout.tv_sec = now.tv_sec + 5;
timeout.tv_nsec = now.tv_usec * 1000;

But I found it won't work without modification, in Linux, it complain
gettimeofday() needs another parameter
(something like timezone, if I remember well), and in Windows the compiler
complain gettimeofday() is not
defined. So what is the "most" standard or correct way to prepare "timeout"?

Thanks a lot,

Limin

PS, I was trying to send this email by my gmail account,
but it didn't work with this mailling list.

             reply	other threads:[~2005-09-27 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 11:13 Fu Limin [this message]
2005-09-27 13:16 ` Dmitrii Sernii
     [not found]   ` <1130.130.192.136.198.1127830895.squirrel@130.192.136.198>
2005-09-27 15:49     ` Dmitrii Sernii
2005-09-28  8:38       ` Fu Limin
  -- strict thread matches above, loose matches on Subject: below --
2002-07-22 21:19 Nir Nizry
2002-07-24  0:31 ` Ross Johnson
2002-07-31  0:13 ` Ross Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1402.130.192.136.198.1127819578.squirrel@130.192.136.198 \
    --to=limin.fu@ircc.it \
    --cc=pthreads-win32@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).