Date: Mon, 16 Oct 2006 15:25:48 -0400 From: John Baldwin <jhb@freebsd.org> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: freebsd-current@freebsd.org, "Sean C. Farley" <sean-freebsd@farley.org> Subject: Re: Fix for memory leak in setenv/unsetenv Message-ID: <200610161525.49212.jhb@freebsd.org> In-Reply-To: <20061015091244.GC1239@turion.vk2pj.dyndns.org> References: <20061006200320.T1063@baba.farley.org> <200610101001.04286.jhb@freebsd.org> <20061015091244.GC1239@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 15 October 2006 05:12, Peter Jeremy wrote: > On Tue, 2006-Oct-10 10:01:03 -0400, John Baldwin wrote: > >I know for one app at my last job we had a problem with this with TZ, and so > >we explicitly space padded the timezone name out to a fixed-size each time > >to avoid the leak. > > Funny, it was a problem with TZ that led me to raise the PR initially. > I think I came up with the same work-around. Heh. > It's a pity that there's no truely re-entrant interface to the > ctime(3) family (ie, one that allows you to specify the timezone as > a parameter). Yes. :( That is the real hack I think, having to modify the environment to make ctime() DTRT. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610161525.49212.jhb>