[asterisk-dev] DEBUG_THREADS and unreleased locks

[Norman Franke]

> Another thing you can do is to not set a breakpoint, but to just  
> get a backtrace
> of the SIP monitor thread when you have it in this state.  Then,  
> you can see if
> it's somewhere where it makes sense to still be holding a channel  
> lock.

I did that and it seemed OK.

Further searching in the logs, I found this:

[Jan 31 14:39:06] ERROR[29511]: /usr/src/asterisk-1.4.17/include/ 
asterisk/lock.h:271 __ast_pthread_mutex_destroy: channel.c line 1248  
(ast_channel_free): Error: attempt to destroy locked mutex '&chan- 
 >lock'.
[Jan 31 14:39:06] ERROR[29511]: /usr/src/asterisk-1.4.17/include/ 
asterisk/lock.h:274 __ast_pthread_mutex_destroy: channel.c line 5012  
(ast_channel_trylock): Error: '&chan->lock' was locked here.
[Jan 31 14:39:06] ERROR[29511]: /usr/src/asterisk-1.4.17/include/ 
asterisk/lock.h:281 __ast_pthread_mutex_destroy: channel.c line 1248  
(ast_channel_free): Error destroying mutex &chan->lock: Device or  
resource busy

> However, I know that there have been multiple related fixes since  
> 1.4.17, so I
> would encourage you to go ahead and update to the latest release  
> candidate for
> 1.4.18 and see if you still have a problem.


OK, I've upgraded and we'll see how this goes today.

Norman Franke
Answering Service for Directors, Inc.
www.myasd.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20080201/b0db749d/attachment.htm