Date: Mon, 3 Dec 2007 03:43:38 -0800 From: "Carl Shapiro" <carl.shapiro@gmail.com> To: "Kostik Belousov" <kostikbel@gmail.com> Cc: freebsd-current@freebsd.org, David Xu <davidxu@freebsd.org> Subject: Re: Serious compatibility breakage in -current. Message-ID: <4dcb5abd0712030343x5b5b6d6dj239a79323d0dfad8@mail.gmail.com> In-Reply-To: <20071203092755.GT83121@deviant.kiev.zoral.com.ua> References: <20071130162409.C8D3D5B59@mail.bitblocks.com> <47536718.1020107@freebsd.org> <20071203092755.GT83121@deviant.kiev.zoral.com.ua>
index | next in thread | previous in thread | raw e-mail
On Dec 3, 2007 1:27 AM, Kostik Belousov <kostikbel@gmail.com> wrote: > The problem, as for now, is not with the POSIX-ing the signal delivered, > that seems to be right. The ABI breakage introduced causes troubles. Actually, the change fell short of POSIX compliance. FreeBSD went from one form of non-compliance to another. It is nice that the protection violation signal is consistent with the standard, but this is not enough. See Bakul's message earlier in the thread.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4dcb5abd0712030343x5b5b6d6dj239a79323d0dfad8>
