From owner-freebsd-stable@FreeBSD.ORG Wed Mar 28 23:20:01 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A950516A401 for ; Wed, 28 Mar 2007 23:20:01 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6CB5F13C469 for ; Wed, 28 Mar 2007 23:20:01 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.14.0/8.14.0/NETPLEX) with ESMTP id l2SNK0YH016083; Wed, 28 Mar 2007 19:20:00 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.ntplx.net [204.213.176.10]); Wed, 28 Mar 2007 19:20:00 -0400 (EDT) Date: Wed, 28 Mar 2007 19:20:00 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Steve Watt In-Reply-To: <200703282200.l2SM0OG2060016@wattres.watt.com> Message-ID: References: <665184.92983.qm@web32901.mail.mud.yahoo.com> <200703282200.l2SM0OG2060016@wattres.watt.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Pthreads signals X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2007 23:20:01 -0000 On Wed, 28 Mar 2007, Steve Watt wrote: > > In , > Daniel Eischen wrote: >> On Wed, 28 Mar 2007, Peter Holmes wrote: >> >>> How do signals work with pthreads in FreeBSD. How are process signals >>> delivered? >> >> The best explanation of signals and threads in general >> is in the POSIX spec, or Butenhof's book. >> >> http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html > > I suspect the question was rather more specific than that, due to > bad experiences with LinuxThreads. Does FreeBSD have a proper > signal delivery model, where thread masks are per-signal, and signals > sent to the process when all threads within the process have the > signal blocked remain pending against the process so any thread may > accept the signal using sigwait()/sigtimedwait()/sigwaintinfo(). These are POSIX threads, so if things don't behave as specified by or as allowed by the standard, a bug report should be filed. -- DE