From owner-freebsd-hackers Mon Nov 24 15:29:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA15412 for hackers-outgoing; Mon, 24 Nov 1997 15:29:33 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA15392 for ; Mon, 24 Nov 1997 15:29:21 -0800 (PST) (envelope-from alex@zen.nash.org) Received: (from alex@localhost) by zen.nash.org (8.8.8/8.8.7) id RAA00644; Mon, 24 Nov 1997 17:25:25 -0600 (CST) (envelope-from alex) Message-Id: <199711242325.RAA00644@zen.nash.org> Date: Mon, 24 Nov 1997 17:25:25 -0600 (CST) From: Alex Nash Reply-To: nash@mcs.com Subject: Re: pthread_cond_timedwait returning wrong error? To: deischen@iworks.InterWorks.org cc: julian@whistle.com, nash@mcs.com, freebsd-hackers@freebsd.org In-Reply-To: <199711240452.WAA24529@iworks.InterWorks.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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