[27803] in Kerberos
Re: Memory leakage question
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Sun May 20 22:15:53 2007
In-Reply-To: <20070520122132.02e61b6f.mba2000@ioplex.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <8AF3D6AB-B5E4-40B6-8923-C79026CC8B26@mit.edu>
From: Ken Raeburn <raeburn@mit.edu>
Date: Sun, 20 May 2007 20:59:15 -0400
To: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On May 20, 2007, at 12:21, Michael B Allen wrote:
> In my experience with running valgrind on mechglue, I recall there are
> things that are initialized once when first used and never freed. So
> technically they are leaks and valgrind picks them up but the leaks
> should never grow beyond a fixed size.
It should be possible to load the library with dlopen, use it, do
appropriate cleanup, dlclose it, and do that in a loop a large number
of times without leaking memory. The library finalization function
should free up any global storage retained within the library.
Ken
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
