[27795] in Kerberos
Re: Memory leakage question
daemon@ATHENA.MIT.EDU (Michael B Allen)
Sun May 20 12:21:54 2007
Date: Sun, 20 May 2007 12:21:32 -0400
From: Michael B Allen <mba2000@ioplex.com>
To: "Markus Moeller" <huaraz@moeller.plus.com>
Message-Id: <20070520122132.02e61b6f.mba2000@ioplex.com>
In-Reply-To: <f2n1hh$k5m$1@sea.gmane.org>
Mime-Version: 1.0
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On Sat, 19 May 2007 15:27:16 +0100
"Markus Moeller" <huaraz@moeller.plus.com> wrote:
> as I use GSS_C_NULL_OID_SET mechs will never be freed or is there a way to
> free it from my application ?
Hi Markus,
You mean the static list of mechs? Why do you want to free that? It should
only be initialized once in the lifetime of the library. At least that's
what it looks like from the information you posted.
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.
Mike
PS to kitten: This is another thing that would be more elegant with an
application context.
--
Michael B Allen
PHP Active Directory Kerberos SSO
http://www.ioplex.com/
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
