aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2007-12-07 21:11:44 +0000
committerrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2007-12-07 21:11:44 +0000
commite129f64bc22b5d17388adb1e57212628b91901d2 (patch)
treebe5b685cc540b61a51d3abfc9314dfd70b3bf556 /include
parent087a51990dbc1ed4bc3c80ea754ea915308bce0d (diff)
Merged revisions 91826 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r91826 | russell | 2007-12-07 15:11:08 -0600 (Fri, 07 Dec 2007) | 6 lines 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/trunk@91827 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'include')
-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 c9f4b4eae..d4870b966 100644
--- a/include/asterisk/lock.h
+++ b/include/asterisk/lock.h
@@ -187,7 +187,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;