From owner-freebsd-stable Sat Jan 12 22: 3:15 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-33.dsl.lsan03.pacbell.net [64.169.107.33]) by hub.freebsd.org (Postfix) with ESMTP id 2CFAB37B400 for ; Sat, 12 Jan 2002 22:03:12 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6C57F66E18; Sat, 12 Jan 2002 22:03:11 -0800 (PST) Date: Sat, 12 Jan 2002 22:03:11 -0800 From: Kris Kennaway To: Mark.Andrews@isc.org Cc: Kris Kennaway , alexus , freebsd-stable@freebsd.org Subject: Re: Fw: Cron /usr/local/bin/cvsup -g -h cvsup.FreeBSD.org /usr/share/examples/cvsup/stable-supfile >/dev/null;cd /usr/src;make buildworld >/dev/null;make buildkernel >/dev/null Message-ID: <20020112220311.A923@xor.obsecurity.org> References: <20020112173951.A47715@xor.obsecurity.org> <200201130336.g0D3abp44605@drugs.dv.isc.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200201130336.g0D3abp44605@drugs.dv.isc.org>; from Mark.Andrews@isc.org on Sun, Jan 13, 2002 at 02:36:37PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 13, 2002 at 02:36:37PM +1100, Mark.Andrews@isc.org wrote: > > Yeah, but they're not problems the end user needs to worry about, in > > that they're perfectly normal when compiling FreeBSD. >=20 > So you have performed the call analysis to verify that there > is not a bounds write violation? >=20 > The program is buggy. If someone submitted a patch for BIND > which generated this error I would not accept it as it is. > I'd either send it back to them to correct or fix the calling > sequence myself. I think you're missing my point. Yes, they're probably pieces of code which should be fixed by the developers, but they're not abnormal messages from the FreeBSD build process (since they're there all the time) which the end user needs to take action over. Kris --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8QSMeWry0BWjoQKURAj1rAKCPU+Il7HGHxc1RcqDifyfps+suaQCgjLtY 9lcMv3GFjWOQMHa+QsnYyOE= =CJ1r -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message