[krbdev.mit.edu #5962] SVN Commit

[Ken Raeburn via RT]

A step towards ensuring we check mutex lock attempt results...

Always use inline function k5_mutex_lock_1 instead of gcc statement
expression, even under gcc.

Under gcc 4, declane k5_mutex_lock_1 and krb5int_mutex_lock with attribute
warn_unused_result.

In k5_mutex_destroy macro, only store destroy code source+line if we succeed
in temporarily locking the mutex.
Commit By: raeburn



Revision: 20566
Changed Files:
U   trunk/src/include/k5-thread.h