From owner-freebsd-threads@FreeBSD.ORG Mon Jul 25 19:34:12 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 9106316A41F; Mon, 25 Jul 2005 19:34:12 +0000 (GMT) (envelope-from julian@elischer.org) Received: from postoffice.vicor-nb.com (postoffice.vicor.com [69.26.56.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A20843D46; Mon, 25 Jul 2005 19:34:06 +0000 (GMT) (envelope-from julian@elischer.org) Received: from localhost (localhost [127.0.0.1]) by postoffice.vicor-nb.com (Postfix) with ESMTP id 897BD4CE7B7; Mon, 25 Jul 2005 12:34:06 -0700 (PDT) Received: from postoffice.vicor-nb.com ([127.0.0.1]) by localhost (postoffice.vicor-nb.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95779-05; Mon, 25 Jul 2005 12:34:06 -0700 (PDT) Received: from [208.206.78.97] (julian.vicor-nb.com [208.206.78.97]) by postoffice.vicor-nb.com (Postfix) with ESMTP id 1D6A24CE910; Mon, 25 Jul 2005 12:34:06 -0700 (PDT) Message-ID: <42E53EAD.4030205@elischer.org> Date: Mon, 25 Jul 2005 12:34:05 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050629 X-Accept-Language: en, hu MIME-Version: 1.0 To: Daniel Eischen References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postoffice.vicor.com Cc: Ady_Li@trendmicro.com.cn, Roman Streltsov , freebsd-threads@freebsd.org Subject: Re: system scope threads entering STOP state X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2005 19:34:12 -0000 Daniel Eischen wrote: >On Sun, 24 Jul 2005, Julian Elischer wrote: > > > >>it may be worth looking at libthr too >>as it (the alternate threading library) >>is sufficiently different in this regard. >> >> > >If there's a problem with libpthread, I suspect it's in the >kernel, so it should be present for libthr as well. The user >library does nothing special for SIGSTOP nor waitXXX(). > > but the kernel handles signals differently between the two threading models so different code paths are followed which measn that it may be an instructive experiment.