[27796] in Kerberos

home help back first fref pref prev next nref lref last post

Re: Memory leakage question

daemon@ATHENA.MIT.EDU (Markus Moeller)
Sun May 20 12:42:35 2007

To: kerberos@mit.edu
From: "Markus Moeller" <huaraz@moeller.plus.com>
Date: Sun, 20 May 2007 17:40:46 +0100
Message-ID: <f2pto6$q9u$1@sea.gmane.org>
Mime-Version: 1.0
X-Complaints-To: usenet@sea.gmane.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu


"Michael B Allen" <mba2000@ioplex.com> wrote in message news:20070520122132.02e61b6f.mba2000@ioplex.com...
> 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.

That is what I wasn't sure about.

>
> 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/
> ________________________________________________

Thanks 
Markus
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post