From owner-freebsd-current Wed Apr 22 21:43:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00466 for freebsd-current-outgoing; Wed, 22 Apr 1998 21:43:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from prairiecomm.prairiecommunications.com (mail.prairiecommunications.com [208.141.230.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00455 for ; Wed, 22 Apr 1998 21:42:53 -0700 (PDT) (envelope-from alk@pobox.com) Received: from 208.141.230.118 by prairiecomm.prairiecommunications.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id JN78H1XF; Wed, 22 Apr 1998 23:38:19 -0500 Received: (from alk@localhost) by pobox.com (8.8.8/8.7.3) id XAA17035; Wed, 22 Apr 1998 23:44:56 -0500 (CDT) Date: Wed, 22 Apr 1998 23:44:56 -0500 (CDT) Message-Id: <199804230444.XAA17035@pobox.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: jb@cimlogic.com.au Subject: Re: pthread_mutex_lock References: <199804222228.RAA15757@compound.east.sun.com> <199804222234.IAA00643@cimlogic.com.au> X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth John Birrell on Thu, 23 April: : : It blocks. pthread_mutex_trylock is the one that doesn't block. : Which man page says otherwise? This is amusing. pthread(3) says otherwise: int pthread_mutex_lock(pthread_mutex_t *mutex) Try to lock a mutex, but don't block if the mutex is locked by another thread, including the current thread. But *only* if I use xemacs 20.3's (manual-entry "pthread(3)"). My apologies for the noise. The elisp clean-up code is apparently broken. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message