Date: Wed, 28 Mar 2007 19:20:00 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Steve Watt <steve@Watt.COM> Cc: freebsd-stable@freebsd.org Subject: Re: Pthreads signals Message-ID: <Pine.GSO.4.64.0703281917520.16603@sea.ntplx.net> In-Reply-To: <200703282200.l2SM0OG2060016@wattres.watt.com> References: <665184.92983.qm@web32901.mail.mud.yahoo.com> <200703282200.l2SM0OG2060016@wattres.watt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 28 Mar 2007, Steve Watt wrote: > > In <Pine.GSO.4.64.0703281615540.14519@sea.ntplx.net>, > Daniel Eischen <deischen@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0703281917520.16603>