[asterisk-bugs] [Asterisk 0015862]: chan_sip deadlock in mutex sip_alloc

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Oct 2 17:53:51 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15862 
====================================================================== 
Reported By:                zerohalo
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   15862
Category:                   Channels/chan_sip/General
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.26.2 
JIRA:                       SWP-209 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-09 08:14 CDT
Last Modified:              2009-10-02 17:53 CDT
====================================================================== 
Summary:                    chan_sip deadlock in mutex sip_alloc
Description: 
output of core show locks and backtrace from a forced crash attached.
====================================================================== 

---------------------------------------------------------------------- 
 (0111811) dvossel (administrator) - 2009-10-02 17:53
 https://issues.asterisk.org/view.php?id=15862#c111811 
---------------------------------------------------------------------- 
I don't see a dead lock here. One thread holds two locks and isn't waiting
on any other locks... And the other two threads are waiting on one of the
locks the first one has, but I don't see anything obvious that is
preventing that thread from giving up the lock.

Also, how is this a "forced crash". Are there steps we can use to
reproduce this behavior? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-02 17:53 dvossel        Note Added: 0111811                          
======================================================================




More information about the asterisk-bugs mailing list