aboutsummaryrefslogtreecommitdiffstats
path: root/utils
diff options
context:
space:
mode:
authorrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2008-02-28 22:39:26 +0000
committerrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2008-02-28 22:39:26 +0000
commit020573b8ac5cacaef68586712538067febee0d67 (patch)
tree897a726d01e6359400224e1db3450880fcfe68ab /utils
parentd4718af66edfa3f0a64dc8a92cf24c8215fcb635 (diff)
Merged revisions 105116 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r105116 | russell | 2008-02-28 16:23:05 -0600 (Thu, 28 Feb 2008) | 8 lines Fix a bug in the lock tracking code that was discovered by mmichelson. The issue is that if the lock history array was full, then the functions to mark a lock as acquired or not would adjust the stats for whatever lock is at the end of the array, which may not be itself. So, do a sanity check to make sure that we're updating lock info for the proper lock. (This explains the bizarre stats on lock #63 in BE-396, thanks Mark!) ........ git-svn-id: http://svn.digium.com/svn/asterisk/trunk@105144 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'utils')
-rw-r--r--utils/check_expr.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/utils/check_expr.c b/utils/check_expr.c
index 00d00d802..009fe8673 100644
--- a/utils/check_expr.c
+++ b/utils/check_expr.c
@@ -93,8 +93,8 @@ void ast_store_lock_info(enum ast_lock_type type, const char *filename,
/* not a lot to do in a standalone w/o threading! */
}
-void ast_mark_lock_acquired(void);
-void ast_mark_lock_acquired(void)
+void ast_mark_lock_acquired(void *);
+void ast_mark_lock_acquired(void *foo)
{
/* not a lot to do in a standalone w/o threading! */
}