On Dec 13, 2005, at 16:20, Jon DeVree wrote:
#13 0xb7e0afe6 in pthread_mutex_lock () from
/lib/tls/i686/cmov/libc.so.6
#14 0xb7ed7b4a in krb5_fcc_initialize (context=0x804d088,
id=0x804d290,
princ=0x8052c48) at ../../../../src/lib/krb5/ccache/cc_file.c:1423
1423: kret = k5_mutex_lock(&((krb5_fcc_data *) id->data)->lock);
Could you show me what the "lock" field (a structure) contains at
this point? There should be a couple of fields indicating where the
lock was previously acquired.
I've skimmed cc_file.c but didn't spot any place where we're likely
to leave a mutex locked. (Though I did spot one error path where we
might destroy a locked mutex without unlocking it first, which should
also be fixed.)
Ken
________________________________________________
Kerberos mailing list [email protected]
https://mailman.mit.edu/mailman/listinfo/kerberos
