From owner-freebsd-hackers Sat Feb 6 16:05:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09804 for freebsd-hackers-outgoing; Sat, 6 Feb 1999 16:05:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sturm.canonware.com (canonware.com [204.107.140.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09753 for ; Sat, 6 Feb 1999 16:05:49 -0800 (PST) (envelope-from jasone@canonware.com) Received: from localhost (jasone@localhost) by sturm.canonware.com (8.8.8/8.8.8) with ESMTP id PAA12213; Sat, 6 Feb 1999 15:55:42 -0800 (PST) (envelope-from jasone@canonware.com) Date: Sat, 6 Feb 1999 15:55:42 -0800 (PST) From: Jason Evans To: "Sergey S. Kosyakov" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pthreads and select again In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Feb 1999, Sergey S. Kosyakov wrote: > It seems that multiple select()-s and sleep() or > pthread_cond_timedwait() hang when are used in the same time (of > cause, in different threads). See: http://www.freebsd.org/cgi/query-pr.cgi?pr=8872 There is a bug in the pthread kernel's handling of pthread_cond_timedwait() that can cause bad things to happen. The PR includes a patch that I have been using for way too long now. This may not be what is causing your problem, but it's a good thing to check out. Jason Jason Evans http://www.canonware.com/~jasone Home phone: (650) 856-8204 Work phone: (415) 808-8742 "I once knew a happy medium. Her name was Zohar." - James Foster To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message