From owner-freebsd-current Wed Mar 14 4:36: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mf103.infoweb.ne.jp (mf103.infoweb.ne.jp [210.131.99.50]) by hub.freebsd.org (Postfix) with ESMTP id 3AE0737B718 for ; Wed, 14 Mar 2001 04:35:57 -0800 (PST) (envelope-from fwkg7679@mb.infoweb.ne.jp) Received: from amdk6 by mf103.infoweb.ne.jp (8.9.3+3.2W/3.7W-10/13/99) with SMTP id VAA01351; Wed, 14 Mar 2001 21:35:33 +0900 Message-Id: <200103141235.VAA01351@mf103.infoweb.ne.jp> Date: Wed, 14 Mar 2001 21:37:40 +0900 From: KUROSAWA Takahiro To: James FitzGibbon Cc: eischen@vigrid.com, current@freebsd.org Subject: Re: Fixed - pthread altsigstack problem In-Reply-To: <20010312184616.A25098@ehlo.com> References: <20010312184616.A25098@ehlo.com> X-Mailer: Sylpheed version 0.4.62cvs11 (GTK+ 1.2.8; i386-pc-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Mar 2001 18:46:16 -0500 James FitzGibbon wrote: > Both of the patches below fix the problem mentioned in PR bin/25110. The > first one fixes it inside of kern_fork.c and would appear to apply the > corrective behaviour regardless of whether the process uses libc_r or not. The first patch that I sent to you makes the SS_DISABLE flag setting be inherited to the child process (especially when the parent have cleared the flag), as I had mentioned in the mail to -current: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=332928+0+archive/2001/freebsd-current/20010304.freebsd-current I'm not sure that the SS_DISABLE flag setting should be inherited to the child process, but at least I can say the behavior of 5-CURRENT (and 4-STABLE) is different from that of Solaris 7, NetBSD 1.5 and FreeBSD 3.5-STABLE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message