From owner-freebsd-threads@FreeBSD.ORG Wed Sep 29 13:23:48 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0372016A4CE for ; Wed, 29 Sep 2004 13:23:48 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBF4A43D46; Wed, 29 Sep 2004 13:23:47 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) i8TDNk0R059192; Wed, 29 Sep 2004 13:23:47 GMT (envelope-from davidxu@freebsd.org) Message-ID: <415AB791.10809@freebsd.org> Date: Wed, 29 Sep 2004 21:24:33 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.1) Gecko/20040730 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: <16728.37731.540143.307772@grasshopper.cs.duke.edu> <41589B4A.9080508@elischer.org> In-Reply-To: <41589B4A.9080508@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Andrew Gallatin cc: freebsd-threads@freebsd.org Subject: Re: easy to reproduce unkillable threads X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 13:23:48 -0000 Julian Elischer wrote: > > hmm looks like the problem is that the condition variable respods to a > masked signal > > > the signals are all masked from the perspective of the thread..the > signal is delivered to the signal > catcher thread so the UTS can handle it but in the meanwhile the > thread has done a RESTART.. > > David: check out what happens when a signal is delivered to a worker > thread that is in a cv_wait_signal() > Please tell me easiest way to reproduce it, I tried best to reproduce it, but still got nothing. >> >>> . >>> >> >> I haven't checked it as yet but I am starting to see some hint of >> some problem.. >> The fact that cv_wait_signal() reacts to a blocked signal surproses >> me.. >> (according to teh man page) >> >> http://people.freebsd.org/~gallatin/threadlock.tgz >> I use this test case.