There is a memory leak here, if a thread has registered some per-thread data
authorKen Raeburn <raeburn@mit.edu>
Wed, 9 Feb 2005 00:41:40 +0000 (00:41 +0000)
committerKen Raeburn <raeburn@mit.edu>
Wed, 9 Feb 2005 00:41:40 +0000 (00:41 +0000)
commit36f1eda337a7fbbdb53fd0b2c92e2f32085aca78
tree47daf07ae46e4b73735d5b3f221a86188f2a747b
parentf3b4130dd148ad823d7844caa4253a76968ddf68
There is a memory leak here, if a thread has registered some per-thread data
when we delete the key.  Fixing it will require walking through the per-thread
data of every thread and freeing the objects... and watching for deadlocks in
the case where a thread is exiting at the same time.

* threads.c (k5_key_delete) [pthread case]: Reset flags and destructor function
pointer to unset state.
(krb5int_thread_support_init, krb5int_thread_support_fini): If
SHOW_INITFINI_FUNCS is defined, print some tracing messages.

ticket: 2916
status: open

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@17092 dc483132-0cff-0310-8789-dd5450dbe970
src/util/support/ChangeLog
src/util/support/threads.c