From owner-freebsd-current Tue Nov 10 07:16:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04349 for freebsd-current-outgoing; Tue, 10 Nov 1998 07:16:32 -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 HAA04344 for ; Tue, 10 Nov 1998 07:16:29 -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 JAA20439; Tue, 10 Nov 1998 09:16:04 -0600 (CST) Message-Id: <199811101516.JAA20439@ns.tar.com> From: "Richard Seaman, Jr." To: "Brian Feldman" Cc: "current@freebsd.org" Date: Tue, 10 Nov 98 09:16:04 -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 On Fri, 6 Nov 1998 21:27:50 -0500 (EST), Brian Feldman wrote: >I suppose it is. LinuxThreads don't work tho... I need %@#!^ testers! I looked briefly at your code, and I have a question. I understand that the "flags" argument to the clone call takes a signal number in the low order 8 bits of flags. This is the signal to be sent to the parent on exit of the thread. I can see where you implement signal sharing, but not where you record and implement this exit signal handling. Linuxthreads relies on the thread manager thread receiving a "PTHREAD_SIG_RESTART" signal (actually SIGUSR1) when threads exit. Perhaps I've missed something? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message