Ulrich Eckhardt, le Mon 12 Oct 2009 22:15:59 +0200, a écrit : > On Sunday 11 October 2009 12:11:50 Remi Denis-Courmont wrote: > > I would expect cond_timedwait to sleep for the specified interval rather > > than abort (though sleeping in a portable way is not completely trivial). > > Alternative suggestion: If pthread_cond_init() is implemented in the stubs to > return "okay", then I could imagine pthread_cond_[timed]wait() to also work > in > some way.
There's a difference: it's completely correct for a thread-safe library running in a non-threaded app to use pthread_cond_init(). It is also correct to use pthread_cond_signal to signal that a condition is now true. What isn't correct is to use pthread_cond_wait/timedwait() since there is no way pthread_cond_signal() can ever be called. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
