Date: Sat, 02 Oct 1999 19:10:03 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: obrien@freebsd.org Cc: John Polstra <jdp@polstra.com>, Alan Cox <alc@cs.rice.edu>, arch@freebsd.org Subject: Re: Now that sigcontext is gone ... Message-ID: <37F5D9FB.D121CF79@newsguy.com> References: <19990930162834.C20978@nonpc.cs.rice.edu> <XFMail.990930144341.jdp@polstra.com> <19991002011955.A85828@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[redirecting to -arch as a test-case] 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? Well, it won't break any POSIX code, that's sure... :-) I like having the distinction this provides, but since this is stricly freebsd-i386, I'd wager we won't have too much trouble making the change. After all, if freebsd-alpha works ok in a POSIX-compatible way... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Rule 69: Do unto other's code as you'd have it done unto yours To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37F5D9FB.D121CF79>