From: | epeisach@mit.edu |
Subject: | CVS Commit |
* k5-thread.h (k5_os_mutex_lock): Under Irix, invoke
k5_pthread_mutex_lock() with the k5_os_mutex, not the
pthread_mutex_t.
(k5_pthread_assert_locked,unlocked): If DEBUG_THREADS not used, provide
correct prototype. Add missing close paren.
Test programs show that under irix, the mutex locking/unlocking code was
working - even with the wrong memory use... I do not understand why.
To generate a diff of this commit:
cvs diff -r1.489 -r1.490 krb5/src/include/ChangeLog
cvs diff -r1.27 -r1.28 krb5/src/include/k5-thread.h
k5_pthread_mutex_lock() with the k5_os_mutex, not the
pthread_mutex_t.
(k5_pthread_assert_locked,unlocked): If DEBUG_THREADS not used, provide
correct prototype. Add missing close paren.
Test programs show that under irix, the mutex locking/unlocking code was
working - even with the wrong memory use... I do not understand why.
To generate a diff of this commit:
cvs diff -r1.489 -r1.490 krb5/src/include/ChangeLog
cvs diff -r1.27 -r1.28 krb5/src/include/k5-thread.h