From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15585 invoked by alias); 19 Jun 2008 05:58:06 -0000 Received: (qmail 15574 invoked by uid 22791); 19 Jun 2008 05:58:04 -0000 X-Spam-Check-By: sourceware.org Received: from wilbur.25thandClement.com (HELO wilbur.25thandClement.com) (208.96.11.245) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 19 Jun 2008 05:57:46 +0000 Received: from wilbur.25thandClement.com (william@localhost.25thandClement.com [127.0.0.1]) by wilbur.25thandClement.com (8.14.0/8.13.8) with ESMTP id m5J5vinx016536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 18 Jun 2008 22:57:44 -0700 (PDT) Received: (from william@localhost) by wilbur.25thandClement.com (8.14.0/8.14.0/Submit) id m5J5viRI011022 for pthreads-win32@sourceware.org; Wed, 18 Jun 2008 22:57:44 -0700 (PDT) Date: Thu, 19 Jun 2008 05:58:00 -0000 From: William Ahern To: pthreads-win32@sourceware.org Subject: sigaction & pthread_sigmask Message-ID: <20080619055744.GA19869@wilbur.25thandClement.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (wilbur.25thandClement.com [127.0.0.1]); Wed, 18 Jun 2008 22:57:45 -0700 (PDT) X-IsSubscribed: yes Mailing-List: contact pthreads-win32-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sourceware.org X-SW-Source: 2008/txt/msg00031.txt.bz2 Would it be worthwhile to submit a sigaction, sigwait, sigprocmask, pthread_sigmask patch? Or are signals strictly outside the scope of the project? I'm working on sigaction and sigwait implementations--using atomic CAS operations for async-safety--intended for a portable kqueue library. But the library depends on pthreads-w32 anyhow, and it would be cleaner to simply patch upstream.