[asterisk-bugs] [Asterisk 0014100]: Segfault in chan_sip

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14100 
====================================================================== 
Reported By:                jsmith
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   14100
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1-beta3 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-12-17 08:10 CST
Last Modified:              2008-12-17 14:50 CST
====================================================================== 
Summary:                    Segfault in chan_sip
Description: 
Running Asterisk 1.6.1-beta3, I get segfaults every few minutes.  The
segfault appears to be happening in chan_sip.  (I will attach a copy of the
backtrace, if it's useful.)
====================================================================== 

---------------------------------------------------------------------- 
 (0096576) jsmith (manager) - 2008-12-17 14:50
 http://bugs.digium.com/view.php?id=14100#c96576 
---------------------------------------------------------------------- 
There is a "thread apply all bt" attached to this ticket.

Additionally, there was *no* useful output on the console, even with
debugging turned up to the max.  This system would crash within 20 seconds
of restarting Asterisk.

For now, I've moved this to a completely different PC and it seems to be
working better (only been up for 15 minutes or so), so we maybe able to
chalk this one up to bad PC hardware.  (The old PC is currently running
memtest86+, but has not shown any errors.)

Go ahead and close this ticket for now... I'll re-open if I can reproduce
on other hardware. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-17 14:50 jsmith         Note Added: 0096576                          
======================================================================