A small enhancement-- I added the routine log_show_lock to utils.c, which if the...
authorSteve Murphy <murf@digium.com>
Wed, 16 Apr 2008 20:54:41 +0000 (20:54 +0000)
committerSteve Murphy <murf@digium.com>
Wed, 16 Apr 2008 20:54:41 +0000 (20:54 +0000)
commit752f6681b1ea748a1acef2a55e17c4c564715fde
tree18e50329931323a287b2b1dff864083062d3cf62
parenta51fb142f9a942e501c0e4400d94183504f68335
A small enhancement-- I added the routine log_show_lock to utils.c, which if the mentioned lock has been acquired, this routine will log to the console the normal info about that lock you'd see from the CLI when you do a 'core show locks'. It's solely for debug-- if the lock is NOT acquired, there is no output. I use it to show 'unexpected' locks, to see where/why a lock is pre-locked. This command is to be called from points of interest, like just before a trylock, and helps to spot fleeting, highly temporal locks that normally are not locked...

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@114187 65c4cc65-6c06-0410-ace0-fbb531ad65f3
include/asterisk/lock.h
main/utils.c