Date: Sun, 19 Oct 2003 15:48:58 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: __fpclassifyd problem Message-ID: <20031019224858.GA64932@rot13.obsecurity.org> In-Reply-To: <20031019221341.GA32851@troutmask.apl.washington.edu> References: <3F92E129.10307@veidit.net> <20031019204629.GC49466@rot13.obsecurity.org> <3F92FC99.8010802@freebsd.org> <20031019221341.GA32851@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 19, 2003 at 03:13:41PM -0700, Steve Kargl wrote: > I sent in an email *along time ago* about this type=20 > of problem. See the fallout due to revision 1.24 > of lib/libc/stdio/findfp.c. IMHO, all shared libraries > versions should have been bumped in going from 4.x to > 5.0.=20 You don't want to do it before you have to, because this creates more pain for people when you make a change that breaks backwards compat (given the policy/preference of only bumping once per major release). I'm working on a script that will detect the kind of backwards compatibility breakage we're seeing here by comparing the symbols in 4.x and 5.x versions of libraries with the same major revision. We can then run this once a day/week/whatever somewhere to catch these problems as soon as they occur in future. Kris --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/kxTaWry0BWjoQKURAjfYAJ48VKLg8WnXH3BOw+PoEMj9lVVZowCeI0Kt zttxkEO3OYQfhFF9jVCVgrQ= =vmzO -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031019224858.GA64932>