[asterisk-bugs] [Asterisk 0015544]: Segfault in SVN revision 207360 chan_sip.c in in __ast_pthread_mutex_lock

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15544 
====================================================================== 
Reported By:                aragon
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   15544
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                       SWP-270 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 207360 
Request Review:              
====================================================================== 
Date Submitted:             2009-07-21 08:03 CDT
Last Modified:              2009-11-06 15:18 CST
====================================================================== 
Summary:                    Segfault in SVN revision 207360 chan_sip.c in in
__ast_pthread_mutex_lock
Description: 
Crashed here

0x00697412 in __ast_pthread_mutex_lock (filename=0x6f1e35 "chan_sip.c",
    lineno=1935, func=0x6f23c4 "retrans_pkt",
    mutex_name=0x6f23d0 "&pkt->owner->lock", t=0x40)
    at /dar/build/asterisk-1.4.26/include/asterisk/lock.h:354

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0015543 Segfault in SVN revision 207360 chan_sip.c
====================================================================== 

---------------------------------------------------------------------- 
 (0113345) jpeeler (administrator) - 2009-11-06 15:18
 https://issues.asterisk.org/view.php?id=15544#c113345 
---------------------------------------------------------------------- 
A "thread apply all bt" would be helpful as well as checking the address of
pkt->owner (p pkt->owner in frame 0). For one of the backtraces the lock
address is definitely invalid. Console debug output would also help. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-06 15:18 jpeeler        Note Added: 0113345                          
======================================================================