From owner-freebsd-bugs Tue Mar 2 1:40:18 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8414F14D21 for ; Tue, 2 Mar 1999 01:40:16 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id BAA58207; Tue, 2 Mar 1999 01:40:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 2 Mar 1999 01:40:01 -0800 (PST) Message-Id: <199903020940.BAA58207@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: bin/10341: memory leak in setenv(3) Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/10341; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@FreeBSD.ORG, peter.jeremy@alcatel.com.au Cc: Subject: Re: bin/10341: memory leak in setenv(3) Date: Tue, 2 Mar 1999 20:33:19 +1100 >>Synopsis: memory leak in setenv(3) >... > [The problem showed up because I have an application which needs to > convert times across multiple timezones, which requires the `TZ' > environment variable to be regularly changed] I think there is already a PR by archie about this (with incomplete or wrong fixes attached). IIRC, it is impossible to fix completely, since some callers keep pointers into the environment, so the environment can't be realloc()ed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message