Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 May 2006 08:56:37 -0400 (EDT)
From:      Daniel Eischen <deischen@freebsd.org>
To:        Alin-Adrian Anton <aanton@spintech.ro>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: which running thread gests the external signal
Message-ID:  <Pine.GSO.4.64.0605030848260.6093@sea.ntplx.net>
In-Reply-To: <44589A77.7070707@spintech.ro>
References:  <4456A5B3.2010809@spintech.ro> <Pine.GSO.4.64.0605012044390.25456@sea.ntplx.net> <44579DE0.1050207@spintech.ro> <Pine.GSO.4.64.0605021400420.414@sea.ntplx.net> <44589A77.7070707@spintech.ro>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 May 2006, Alin-Adrian Anton wrote:

> Daniel Eischen wrote:
>> You are entirely confused.  You should go back to the POSIX standard
>> and get Dave Butenhof's Programming with POSIX Threads book.
>> 
> [..]
>
> You are right. All is clear now, i re-read the link twice and played with 
> sigprocmask vs. pthread_sigmask. It's clear now, also with the help of:
>
> http://www.opengroup.org/onlinepubs/009695399/functions/sigprocmask.html

Note that sigprocmask() and pthread_sigprocmask() are equivalent.  I
don't even think pthread_sigprocmask() is in the standard any longer
(it used to be in an older version of the standard).  New applications
should be using sigprocmask().

-- 
DE



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0605030848260.6093>