Re: Serious compatibility breakage in -current.
- From: "Carl Shapiro" <carl.shapiro@xxxxxxxxx>
- Date: Thu, 29 Nov 2007 22:35:52 -0800
On Nov 29, 2007 3:28 AM, Kostik Belousov <kostikbel@xxxxxxxxx> wrote:
Please, try the patch below and report whether it is enough to fix cmucl
and any other regressions.
With this patch applied old and new binaries are delivered a SIGBUS
instead of SIGSEGV and the si_code is always BUS_ADRERR. This is
halfway between the behavior old binaries expect and the new behavior.
When an access violation occurs, old binaries expect a SIGBUS and an
si_code of BUS_PAGE_FAULT. Presumably, we want new binaries to
receive a SIGSEGV when an access violation occurs. This patch does
not consider whether we are running under an old or new binary. Is
that really okay?
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Serious compatibility breakage in -current.
- From: Kostik Belousov
- Re: Serious compatibility breakage in -current.
- References:
- Serious compatibility breakage in -current.
- From: Carl Shapiro
- Re: Serious compatibility breakage in -current.
- From: Kostik Belousov
- Serious compatibility breakage in -current.
- Prev by Date: Re: [Fwd: Re: kern/118258 sysctl causing panics on 7.0-xxx]
- Next by Date: Re: [Fwd: Re: kern/118258 sysctl causing panics on 7.0-xxx]
- Previous by thread: Re: Serious compatibility breakage in -current.
- Next by thread: Re: Serious compatibility breakage in -current.
- Index(es):