since at opendemand.com
Wed Nov 26 15:53:04 EST 2008
Is there a bug tracking form I can fill out. I do not have the expertise to
fix this issue in a timely manner but I will gladly test any fix.
----- Original Message -----
From: "Ken Raeburn" <raeburn at mit.edu>
To: <jaltman at secure-endpoints.com>
Cc: "krbdev" <krbdev at mit.edu>; "Jeffrey Hutzelman" <jhutz at cmu.edu>
Sent: Saturday, November 22, 2008 12:08 PM
Subject: Re: rewrite gss_krb5_ccache_name
> On Nov 21, 2008, at 23:57, Jeffrey Altman wrote:
>>>> If that is the case, the real bug here is that the gssapi32.dll
>>>> does not implement a DLL_THREAD_DETACH routine which would free
>>>> any allocated memory stored under the registered TLS keys.
>>> Well, if you're not doing that, you certainly should...
>> Indeed, this should be fixed.
> Looks to me like krb5int_thread_detach_hook should mostly be doing
> that. It's the handler in the support library, but all our TSD use is
> funneled through some bookkeeping in the support library, to improve
> things on platforms where OS handles (TLS indices, pthread keys) on
> TSD may be a limited resource. It ought to be deallocating any
> registered per-thread data, though it looks like maybe the bookkeeping
> data itself isn't properly freed.
> krbdev mailing list krbdev at mit.edu
More information about the krbdev