aboutsummaryrefslogtreecommitdiffstats
path: root/CHANGES
diff options
context:
space:
mode:
authormurf <murf@f38db490-d61c-443f-a65b-d21fe96a405b>2008-07-16 23:53:02 +0000
committermurf <murf@f38db490-d61c-443f-a65b-d21fe96a405b>2008-07-16 23:53:02 +0000
commit865f310167e74f689ce4f84b5bb637475200aaf0 (patch)
treec4355e4b6f30b3bc2c0541983630411a784c0ebe /CHANGES
parentc71ab7923908b96826f40d7f88b5aee67f24c789 (diff)
(closes issue #13089)
Reported by: murf Most of this bug was already fixed by Tilghman before I opened it; Many thanks to Tilghman for his fix in svn version 125794. That fix cleared up some of the fields in the lock_info. This commit changes the address that is stored for the lock in the lock_info struct, so that it is the same as that passed into the locking macros. This makes searching for a lock_info (as in log_show_lock()) by its lock addr possible. The lock_addr field is infinitely more useful if it is the same as what is 'publicly' available outside the lock_info code. Many thanks to kpfleming, putnopvut, and Russell for their invaluable insights earlier today. git-svn-id: http://svn.digium.com/svn/asterisk/trunk@131570 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'CHANGES')
0 files changed, 0 insertions, 0 deletions