Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Nov 2007 22:35:52 -0800
From:      "Carl Shapiro" <carl.shapiro@gmail.com>
To:        "Kostik Belousov" <kostikbel@gmail.com>
Cc:        freebsd-current@freebsd.org, davidxu@freebsd.org
Subject:   Re: Serious compatibility breakage in -current.
Message-ID:  <4dcb5abd0711292235k2bc2af86t45f7268d429c03ad@mail.gmail.com>
In-Reply-To: <20071129112824.GD83121@deviant.kiev.zoral.com.ua>
References:  <4dcb5abd0711290226u69105089ya10526519e5cc12d@mail.gmail.com> <20071129112824.GD83121@deviant.kiev.zoral.com.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 29, 2007 3:28 AM, Kostik Belousov <kostikbel@gmail.com> 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?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4dcb5abd0711292235k2bc2af86t45f7268d429c03ad>