summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKen Raeburn <raeburn@mit.edu>2008-08-25 17:40:58 +0000
committerKen Raeburn <raeburn@mit.edu>2008-08-25 17:40:58 +0000
commit57bd520a5037c2194adefb80cc7c13a06dbee42d (patch)
tree469272edee57ed0a631927bf2c692ff563c63d20
parentfc539b7d38ff1dcf0f28fb76edf8bcdbbed99dea (diff)
downloadkrb5-57bd520a5037c2194adefb80cc7c13a06dbee42d.tar.gz
krb5-57bd520a5037c2194adefb80cc7c13a06dbee42d.tar.xz
krb5-57bd520a5037c2194adefb80cc7c13a06dbee42d.zip
Fix sense of test of lock call preparing to update debug info in
k5_mutex_destroy. Thanks, Ezra. ticket: 6090 git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@20690 dc483132-0cff-0310-8789-dd5450dbe970
-rw-r--r--src/include/k5-thread.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/include/k5-thread.h b/src/include/k5-thread.h
index dbc1a6fd7..e8f2c9957 100644
--- a/src/include/k5-thread.h
+++ b/src/include/k5-thread.h
@@ -693,7 +693,7 @@ static inline int k5_mutex_finish_init_1(k5_mutex_t *m, k5_debug_loc l)
#define k5_mutex_destroy(M) \
(k5_os_mutex_assert_unlocked(&(M)->os), \
krb5int_mutex_report_stats(M), \
- k5_mutex_lock(M) && ((M)->loc_last = K5_DEBUG_LOC, k5_mutex_unlock(M)), \
+ !k5_mutex_lock(M) && ((M)->loc_last = K5_DEBUG_LOC, k5_mutex_unlock(M)), \
k5_os_mutex_destroy(&(M)->os))
#if __GNUC__ >= 4