From owner-freebsd-current Sat Oct 2 4:17:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 35EA914E79; Sat, 2 Oct 1999 04:17:22 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id OAA32252; Sat, 2 Oct 1999 14:17:20 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Sat, 2 Oct 1999 14:17:20 +0300 (EEST) From: Narvi To: "David O'Brien" Cc: John Polstra , Alan Cox , current@FreeBSD.ORG Subject: Re: Now that sigcontext is gone ... In-Reply-To: <19991002011955.A85828@dragon.nuxi.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 On Sat, 2 Oct 1999, David O'Brien wrote: > > > P.S. This also reminds me that FreeBSD is non-standard relative > > > to Linux and all of the major vender commercial Unices in that a disallowed > > > access, such as a write to a read-only region of memory, generates > > > a SIGBUS rather than a SIGSEGV. > > > > Yes, this even violates the 1996 POSIX spec. > > So lets make the change for 4.0. :-) > > Just how much code will break? > All that has been changed during porting to catch the other signal? And what will we be issuing sigbus for? > -- > -- David (obrien@NUXI.com) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message