aboutsummaryrefslogtreecommitdiffstats
path: root/include/asterisk/lock.h
diff options
context:
space:
mode:
authorrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2007-12-07 21:11:08 +0000
committerrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2007-12-07 21:11:08 +0000
commit0d4f49f97e38b2755cd1fb63f5e81093d8fa6c45 (patch)
tree0eaee9926b8707eb70e4eee939573cb53410a656 /include/asterisk/lock.h
parentbbcfb01c0a5f59a955fc98ad2775e5668e45fc24 (diff)
I love fixing lock related errors in the lock debugging code. That's about as
ironic as it gets in Asterisk programming land. Anyway, I spotted this bug while trying to track down why systems are locking up and acting weird in issue #11080. The mutex attribute object was marked as static in this function when it should not have been. git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@91826 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'include/asterisk/lock.h')
-rw-r--r--include/asterisk/lock.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/asterisk/lock.h b/include/asterisk/lock.h
index d9e5ec372..629239843 100644
--- a/include/asterisk/lock.h
+++ b/include/asterisk/lock.h
@@ -180,7 +180,7 @@ static inline void ast_reentrancy_unlock(ast_mutex_t *p_ast_mutex)
static inline void ast_reentrancy_init(ast_mutex_t *p_ast_mutex)
{
int i;
- static pthread_mutexattr_t reentr_attr;
+ pthread_mutexattr_t reentr_attr;
for (i = 0; i < AST_MAX_REENTRANCY; i++) {
p_ast_mutex->file[i] = NULL;