Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Nov 1997 17:25:25 -0600 (CST)
From:      Alex Nash <nash@mcs.com>
To:        deischen@iworks.InterWorks.org
Cc:        julian@whistle.com, nash@mcs.com, freebsd-hackers@freebsd.org
Subject:   Re: pthread_cond_timedwait returning wrong error?
Message-ID:  <199711242325.RAA00644@zen.nash.org>
In-Reply-To: <199711240452.WAA24529@iworks.InterWorks.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 23 Nov, Daniel M. Eischen wrote:
> One last question.  The other GNAT targets (Linux, Open/VMS,
> RTEMS, etc) all seem to want the errno to be _returned_ by
> pthread_cond_timedwait (and a couple of others too).  This
> seems wrong, -1 should be returned, and the error code should
> be retrieved from the thread-safe errno.  What does the POSIX
> spec say about the return value of pthread_cond_timedwait()?

The spec says that the error code is returned from the function
directly, and not via errno.  Unfortunately our threads library
appears to return -1 and set errno instead.

Alex





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711242325.RAA00644>