From owner-freebsd-stable Sun Jan 13 6:24: 0 2002 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 2155037B400 for ; Sun, 13 Jan 2002 06:23:56 -0800 (PST) Received: from isc.org (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.6/8.11.2) with ESMTP id g0DENGs00755; Mon, 14 Jan 2002 01:23:17 +1100 (EST) (envelope-from marka@isc.org) Message-Id: <200201131423.g0DENGs00755@drugs.dv.isc.org> To: Kris Kennaway Cc: Mark_Andrews@isc.org, alexus , freebsd-stable@freebsd.org From: Mark.Andrews@isc.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 In-reply-to: Your message of "Sat, 12 Jan 2002 22:03:11 -0800." <20020112220311.A923@xor.obsecurity.org> Date: Mon, 14 Jan 2002 01:23:16 +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 > 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 > Except not all of them are there all the time. There are changes to the code base and these changes can generate new warnings that happen to be over looked because of all the other warnings that are being ignored. The problem is to be able to tell which warning falls into which category. It it the same old warning or is it a new one that really should be addressed. Mark -- Mark Andrews, Internet Software Consortium 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@isc.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message