Date: Sat, 2 Oct 1999 14:17:20 +0300 (EEST) From: Narvi <narvi@haldjas.folklore.ee> To: "David O'Brien" <obrien@FreeBSD.ORG> Cc: John Polstra <jdp@polstra.com>, Alan Cox <alc@cs.rice.edu>, current@FreeBSD.ORG Subject: Re: Now that sigcontext is gone ... Message-ID: <Pine.BSF.3.96.991002141522.86170C-100000@haldjas.folklore.ee> In-Reply-To: <19991002011955.A85828@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.991002141522.86170C-100000>