public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Mikael.Ambrus@elema.siemens.se
To: pthreads-win32@sourceware.cygnus.com
Subject: pthread_cond_timedwait
Date: Thu, 09 Sep 1999 08:51:00 -0000	[thread overview]
Message-ID: <E6002EE20A56D311AA2B00104B4B52214D48FF@mailex.siemens.se> (raw)

	[Ambrus Mikael]  Dear pthreads colleagues, 

	I'm writing a program that uses pthread_cond_timedwait. In the book
that I'm using (Pthreads Programming by Nicols, Buttlar & Proulux Farell )
it says that this function should suspend the thread until some other thread
calls  pthread_cond_signal, pthread_cond_broadcast OR the system timer is
greater than or equal to the third argument (abstime). 

	Since clock_gettime is not implemented and I cant find some other
function that tells me the system time, I've tried to implement my own
version of clock_gettime by using the ansi function clock(). This function
returns the number of ticks that has elapsed since the program was started.

	But it seams that this is not the same absolute time that
pthread_cond_timedwait requires since the thread won't awaken.

	Is there another way to acquire the relevant system time?

	Another thing that has bothered me is that I recently downloaded the
latest snip of phtreads and now my read/write locks won't work. Since the
precompiled lib isn't recognised by the linker (neither with gcc v20.1 nor
MSVC 6.0) for some reason, I built the libs using the buildlib.bat provided.
Here's a snip of the code that fails:

	int pthread_rdwr_wunlock_np (
	   pthread_rdwr_t *rdwrp
	){
	   assert( pthread_mutex_lock(&(rdwrp->mutex)) == 0 );
	   if (rdwrp->writers_writing == 0) {
	      assert( pthread_mutex_unlock(&(rdwrp->mutex)) == 0 );
	      return(-1);            
	   }else{
	      rdwrp->writers_writing = 0;
	      assert(pthread_cond_broadcast(&(rdwrp->lock_free)) == 0);

	   };

	   assert( pthread_mutex_unlock(&(rdwrp->mutex)) == 0 );
	   return(0);
	};

	pthread_cond_broadcast returns EINVAL. Does anyone recognise this
problem?

	Wkr
	Michael Ambrus
	Siemens Elema
>  

             reply	other threads:[~1999-09-09  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-09  8:51 Mikael.Ambrus [this message]
1999-09-09  9:21 ` pthread_cond_timedwait Scott Lightner
1999-09-09 14:07 ` [pthread-win32] pthread_cond_timedwait Tristan Savatier
1999-09-09  9:39 pthread_cond_timedwait Medina, Aurelio
1999-09-09 10:51 pthread_cond_timedwait Bossom, John
2005-06-10 18:07 pthread_cond_timedwait Allan Comar
2005-06-10 20:23 ` pthread_cond_timedwait Steve Croall (TIBCO)
2005-06-11  0:56   ` pthread_cond_timedwait 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=E6002EE20A56D311AA2B00104B4B52214D48FF@mailex.siemens.se \
    --to=mikael.ambrus@elema.siemens.se \
    --cc=pthreads-win32@sourceware.cygnus.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).