[asterisk-bugs] [Asterisk 0012098]: Segmentation fault in chan_sip.c

noreply at bugs.digium.com noreply at bugs.digium.com
Thu Mar 13 18:33:35 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12098 
====================================================================== 
Reported By:                wegbert
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12098
Category:                   Channels/chan_sip/General
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 104334 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-28-2008 09:50 CST
Last Modified:              03-13-2008 18:33 CDT
====================================================================== 
Summary:                    Segmentation fault in chan_sip.c
Description: 
Using svn version from yesterday (svn download reported revision 104534,
'show version on cli reports 'SVN-branch-1.4-r104334'), asterisk crashed
with an segmentation fault:

Program terminated with signal 11, Segmentation fault.
0 0xb7509bfe in __ast_pthread_mutex_lock (filename=0xb755bdf4
"chan_sip.c", lineno=1900, func=0xb755c318 "retrans_pkt", 
    mutex_name=0xb755c324 "&pkt->owner->lock", t=0x0) at
/usr/src/asterisk-1.4/include/asterisk/lock.h:302
302 int canlog = strcmp(filename, "logger.c") & t->track;

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012089 Random crashes in different places
====================================================================== 

---------------------------------------------------------------------- 
 jvandal - 03-13-08 18:33  
---------------------------------------------------------------------- 
Upload info.txt that contain :

show channels concise
sip show channels
core show threads
core show locks


I have now 47 channels still "Up" but the server that generate calls
(asterisk) is shut down, channels must kill if no RTP or whatever, no ?
This is why I suspect a "hidden" locking/infinite loop problem.

I can 'soft hangup' the channel but get theses error (must be normal...)
.

 soft hangup SIP/1584-09ed1d20
Requested Hangup on channel 'SIP/1584-09ed1d20'
[Mar 13 19:35:54] DEBUG[28983]: channel.c:1384 ast_softhangup_nolock:
Soft-Hanging up channel 'SIP/1584-09ed1d20'
[Mar 13 19:35:54] DEBUG[1340]: channel.c:3781 ast_generic_bridge: Didn't
get a frame from channel: SIP/1584-09ed1d20
[Mar 13 19:35:54] DEBUG[1340]: channel.c:4115 ast_channel_bridge: Bridge
stops bridging channels SIP/pbxtest-0a3d1990 and SIP/1584-09ed1d20
[Mar 13 19:35:54] DEBUG[1340]: channel.c:1483 ast_hangup: Hanging up
channel 'SIP/1584-09ed1d20'
[Mar 13 19:35:54] DEBUG[1340]: chan_sip.c:3517 sip_hangup: Hangup call
SIP/1584-09ed1d20, SIP callid
33f2531f7789ed4e124ff8e72853855b at 192.168.99.19)
[Mar 13 19:35:54] DEBUG[1340]: devicestate.c:304
__ast_device_state_changed_literal: Notification of state change to be
queued on device/channel SIP/1584-09ed1d20
[Mar 13 19:35:54] DEBUG[1340]: devicestate.c:304
__ast_device_state_changed_literal: Notification of state change to be
queued on device/channel SIP/1584
[Mar 13 19:35:54] DEBUG[1340]: rtp.c:1511 ast_rtp_early_bridge: Channel
'<unspecified>' has no RTP, not doing anything 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-13-08 18:33  jvandal        Note Added: 0083933                          
======================================================================




More information about the asterisk-bugs mailing list