Summary:	ASTERISK-13237: Segfault in chan_sip
Reporter:	Jared Smith (jsmith)	Labels:
Date Opened:	2008-12-17 08:10:07.000-0600	Date Closed:	2011-06-07 14:00:44
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) backtrace.txt ( 1) sip.conf
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.) ****** ADDITIONAL INFORMATION ****** I'm now testing with the latest 1.6.1 branch, to see if it is any different with regards to the backtrace.
Comments:	By: Jared Smith (jsmith) 2008-12-17 08:49:22.000-0600 Latest version of the 1.6.1 branch from SVN also suffers from the exact same crash.  I can upload the backtrace if you'd like, but the crash is on the exact same line in chan_sip.c. By: Leif Madsen (lmadsen) 2008-12-17 09:19:27.000-0600 Assigned to file because he is such a nice guy! By: Jared Smith (jsmith) 2008-12-17 09:35:02.000-0600 Attached the sip.conf configuration file. By: Jared Smith (jsmith) 2008-12-17 09:58:15.000-0600 Updated sip.conf, as the one I updated earlier was not the correct file. By: Joshua C. Colp (jcolp) 2008-12-17 14:30:59.000-0600 I've tried numerous ways to reproduce this across 32-bit and 64-bit machines. I need more information. Is anything happening when it crashes? Is a call up? I additionally need a thread apply all bt By: Joshua C. Colp (jcolp) 2008-12-17 14:31:39.000-0600 Oh, and console output. By: Jared Smith (jsmith) 2008-12-17 14:50:57.000-0600 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. By: Joshua C. Colp (jcolp) 2008-12-17 15:05:23.000-0600 Suspended per reporter.