From owner-freebsd-hackers Mon Jun 22 01:48:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22155 for freebsd-hackers-outgoing; Mon, 22 Jun 1998 01:48:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22045 for ; Mon, 22 Jun 1998 01:48:11 -0700 (PDT) (envelope-from smoergrd@oslo.geco-prakla.slb.com) Received: from sunw131.oslo.Geco-Prakla.slb.com (sunw131 [134.32.45.97]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id KAA05554 ; Mon, 22 Jun 1998 10:47:39 +0200 (MET DST) Received: by sunw131.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA05668; Mon, 22 Jun 1998 10:47:38 +0200 To: Marino Ladavac Cc: (Dag-Erling Coidan Sm\xrgrav) , hackers@FreeBSD.ORG Subject: Re: Signals in POSIX threads References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 22 Jun 1998 10:47:38 +0200 In-Reply-To: Marino Ladavac's message of Mon, 22 Jun 1998 10:25:48 +0200 (CEST) Message-ID: Lines: 17 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marino Ladavac writes: > However, the thread that does sigwait() on that particular signal will > get it, and nobody else (unless you have another thread sigwait()ing on > that particular signal in which case you are treading the undefined ways. > A nasty issue with sigwait() is that it accepts waits only for a subset > of signals which always have to be asynchronous--it will not wait on SIGFPE, > SIGSEGV and the others which could be delivered through the fault in your > program. These signals will always be delivered to the thread that caused > them (or the currently running thread in case that these signals have been > generated via kill()). Thanks, this was precisely what I was looking for. It doesn't bother me that I can't sigwait() on SIGSEGV and SIGFPE; they're not supposed to occur anyway. -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message