From owner-freebsd-current Thu Aug 6 01:36:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24719 for freebsd-current-outgoing; Thu, 6 Aug 1998 01:36:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles231.castles.com [208.214.165.231]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24708 for ; Thu, 6 Aug 1998 01:36:15 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id BAA01491; Thu, 6 Aug 1998 01:35:04 -0700 (PDT) Message-Id: <199808060835.BAA01491@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mark Huizer cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-reply-to: Your message of "Thu, 06 Aug 1998 10:08:59 +0200." <19980806100859.A312@xaa.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 01:35:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, a nice user of ours pointed me to the fact that various functions > like setenv, putenv etc leak memory like crazy. To mention a very > simple example: > > main(){while(1){setenv("A","AA",1);setenv("A","A",1);}} > > while consume all memory within short periods of time (see setenv.c for > the reason). > > Is this wellknown? I think it is bad, and would like to fix it Not sure, agreed, and please do. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message