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 ([EMAIL PROTECTED]) > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: Now that sigcontext is gone ... Marcel Moolenaar
- Re: Now that sigcontext is gone ... John Polstra
- Re: Now that sigcontext is gone ... Bruce Evans
- Re: Now that sigcontext is gone ... John Polstra
- Re: Now that sigcontext is gone ... Nate Williams
- Re: Now that sigcontext is gone ... Alan Cox
- Re: Now that sigcontext is gone ... John Polstra
- Re: Now that sigcontext is gone ... Alan Cox
- Re: Now that sigcontext is gone ... John Polstra
- Re: Now that sigcontext is gone ... David O'Brien
- Re: Now that sigcontext is gone ... Narvi
- Re: Now that sigcontext is gone ... John Polstra
- Re: Now that sigcontext is g... Thomas David Rivers
- Re: Now that sigcontext is g... Doug Rabson
- Re: Now that sigcontext is g... Bruce Evans
- Re: Now that sigcontext is g... Alan Cox
- Re: Now that sigcontext is g... John Polstra
- Re: Now that sigcontext is g... Garrett Wollman
- Re: Now that sigcontext is gone ... Marcel Moolenaar