aboutsummaryrefslogtreecommitdiffstats
path: root/build_tools
diff options
context:
space:
mode:
authormmichelson <mmichelson@f38db490-d61c-443f-a65b-d21fe96a405b>2008-03-17 22:06:44 +0000
committermmichelson <mmichelson@f38db490-d61c-443f-a65b-d21fe96a405b>2008-03-17 22:06:44 +0000
commit40a42d212f5de330fa13592b0dee9efa8710661f (patch)
tree05ce6f4a3e9a8e2e426097e773cb9675499db3b5 /build_tools
parentc10739a19dd7b8bf09f4cd82b0761f78d426cef3 (diff)
Merged revisions 109226 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r109226 | mmichelson | 2008-03-17 17:05:49 -0500 (Mon, 17 Mar 2008) | 12 lines Fix a logic flaw in the code that stores lock info which is displayed via the "core show locks" command. The idea behind this section of code was to remove the previous lock from the list if it was a trylock that had failed. Unfortunately, instead of checking the status of the previous lock, we were referencing the index immediately following the previous lock in the lock_info->locks array. The result of this problem, under the right circumstances, was that the lock which we currently in the process of attempting to acquire could "overwrite" the previous lock which was acquired. While this does not in any way affect typical operation, it *could* lead to misleading "core show locks" output. ........ git-svn-id: http://svn.digium.com/svn/asterisk/trunk@109227 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'build_tools')
0 files changed, 0 insertions, 0 deletions