Memory leakage question
raeburn at MIT.EDU
Sun May 20 20:59:15 EDT 2007
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.
More information about the Kerberos