From owner-freebsd-current Wed Nov 11 11:52:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26384 for freebsd-current-outgoing; Wed, 11 Nov 1998 11:52:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26377 for ; Wed, 11 Nov 1998 11:52:03 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id NAA17744; Wed, 11 Nov 1998 13:51:34 -0600 (CST) Message-Id: <199811111951.NAA17744@ns.tar.com> From: "Richard Seaman, Jr." To: "Brian Feldman" Cc: "current@freebsd.org" Date: Wed, 11 Nov 98 13:51:33 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: RFSIGSHARE ready? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've looked more closely at your patch. If I understand what it does, it shares signal actions as well as signal masks between threads. Its my understanding that POSIX specifies that signal actions are shared process wide, but that each thread has its own signal mask. It appears to me that this is also what linux threads attempts to implement. If you want POSIX and linux thread compliant signal handling, I would think you would share the p_sigacts structure, but not the p_sigmask structure. However, I have no idea what the linux kernel actually does, so if your goal is to match that, I have no idea if your implementation does that. Also, FYI, your patches break a make buildworld in gdb too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message