From owner-freebsd-current Tue Nov 10 18:22:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23385 for freebsd-current-outgoing; Tue, 10 Nov 1998 18:22:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23378 for ; Tue, 10 Nov 1998 18:22:29 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA14964; Tue, 10 Nov 1998 21:22:06 -0500 (EST) Date: Tue, 10 Nov 1998 21:22:05 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Richard Seaman, Jr." cc: "current@freebsd.org" Subject: Re: RFSIGSHARE ready? In-Reply-To: <199811101516.JAA20439@ns.tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you! On Tue, 10 Nov 1998, Richard Seaman, Jr. wrote: > 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. This is strange... a signal is 5 bits. But I never new this, so thanks for telling me!! I never new this, and this will be absolutely key to getting LinuxThreads working (although this should REALLY be done in user-space... perhaps I shall modify pthread_exit or whatever to send the signal manually and see if that works perfectly. If so, I know where my effort should be going :) > > 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? This doesn't necessarily sound like it's the last bug to be fixed, but it sure could be. Thanks a bunch! Cheers, Brian Feldman > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message