From owner-freebsd-ports Fri Apr 18 16:05:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA10660 for ports-outgoing; Fri, 18 Apr 1997 16:05:53 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA10651 for ; Fri, 18 Apr 1997 16:05:48 -0700 (PDT) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.61 #1) id 0wIMf9-0002eF-00; Fri, 18 Apr 1997 16:01:51 -0700 Date: Fri, 18 Apr 1997 16:01:49 -0700 (PDT) From: Tom Samplonius To: Mike Tancsa cc: ports@freebsd.org Subject: Re: ucd-snmp In-Reply-To: <3.0.1.32.19970418151302.00cc2c10@sentex.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Apr 1997, Mike Tancsa wrote: > At 11:00 AM 4/18/97 -0700, Tom Samplonius wrote: > > > > The ucd-snmp from current or 2.2 doesn't compile on a 2.2.1 system. > >Anyone know how to fix this? > > > > > >cc -I../.. -I../../snmplib -O -Dfreebsd2 -c extensible.c > >extensible.c: In function `var_extensible_mem': > >extensible.c:474: `VM_METER' undeclared (first use this function) > >extensible.c:474: (Each undeclared identifier is reported only once > >extensible.c:474: for each function it appears in.) > >extensible.c:474: initializer element for `mib[1]' is not constant > >*** Error code 1 > > > I was able to compile the package directly from > ftp://ftp.ece.ucdavis.edu/pub/snmp/ucd-snmp.tar.gz > > However, when using the resulting binaries, I some errors/warnings...e.g. > on the snmpwalk I get stuff like > > sand# snmpwalk -v 1 host.to.be.walked.com public > > system.sysDescr.0 = "Livingston PortMaster PM-3 ComOS 3.5c6" > snmpwalk in free(): warning: chunk is already free. > system.sysObjectID.0 = OID: enterprises.307.1.1 > snmpwalk in free(): warning: chunk is already free. > > i.e. after each print, I get the warning message to standard error... I > havent had time to look at it in great detail. > > Anyone have any ideas ? Yes, free() is being called twice for the same block. The new malloc lib complains to stderr when this happens, as it is a sign of bad memory managment by the application. > ---Mike > ********************************************************************** > Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche > Sentex Communications Corp, * To be is to do -- Sartre > Cambridge, Ontario * Do be do be do -- Sinatra > (http://www.sentex.net/~mdtancsa) * > > Tom