From owner-freebsd-current@FreeBSD.ORG Wed Mar 8 15:06:00 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C74A216A420; Wed, 8 Mar 2006 15:06:00 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE52043D62; Wed, 8 Mar 2006 15:05:55 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-3.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Wed, 8 Mar 2006 16:05:54 +0100 Date: Wed, 8 Mar 2006 16:05:54 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Daniel Eischen In-Reply-To: Message-ID: <20060308154805.D10582@beagle.kn.op.dlr.de> References: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-192900866-1141829788=:10582" Content-ID: <20060308155647.Q10582@beagle.kn.op.dlr.de> X-OriginalArrivalTime: 08 Mar 2006 15:05:54.0598 (UTC) FILETIME=[CC0A3460:01C642C1] Cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , current@freebsd.org Subject: Re: When will bsnmp stop breaking -current builds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Mar 2006 15:06:00 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-192900866-1141829788=:10582 Content-Type: TEXT/PLAIN; CHARSET=koi8-r Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: <20060308155647.Y10582@beagle.kn.op.dlr.de> On Wed, 8 Mar 2006, Daniel Eischen wrote: DE>On Wed, 8 Mar 2006, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote: DE> DE>> Harti Brandt writes: DE>> > I checked that gensnmptree does not generated these useless DE>> > references since at least early 2001. DE>> DE>> The machine where I had this problem was running a two-week old DE>> -CURRENT. DE> DE>Same here, give or take a few days. This seems to be exact the time when usr.sbin/bsnmp was detached from=20 world because of my misimport. This was from 2/14/2006 until 2/27/2006. I wonder how this happens... Ok. I think I got it. In Rev. 1.1.1.9 of gensnmptree.c I fixed a bug that= =20 was discovered by jasone: the flag field of struct node was not=20 initialized to 0. This field contains the flags FL_GET and FL_SET. If both= =20 of them are zero, nothing is emitted for that node - this is what should=20 happen to the nodes that reference the op_*dummy() functions. Even with=20 this bug the code happend to work, because this location was 0 with=20 phkmalloc. With the new malloc code the flag field contains obviously a=20 non-zero value. So if you have an old gensnmptree (which may happen=20 because the build of it was detached from world for some time) and a new=20 malloc, you end up getting these references. But for this to happen the build process also must use the installed=20 gensnmptree (because the newly compiled one would not have this bug). Can one of you verify that the new gensnmptree does the right thing?: cd /usr/src/usr.sbin/bsnmpd/gensnmptree make clean make cd /usr/src/contrib/bsnmp/snmpd =2E../gensnmptree