Summary:	ASTERISK-15680: Asterisk 1.2.39 core dump
Reporter:	vieri (vieri)	Labels:
Date Opened:	2010-02-23 12:12:09.000-0600	Date Closed:	2011-06-07 14:00:52
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) core_gdb_2.txt ( 1) core_gdb.txt ( 2) core.gdb.txt.gz ( 3) core2.gdb.txt.gz
Description:	I upgraded Asterisk 1.2.37 to 1.2.39 recently and in the last 2 days I've had 2 segmentation faults and core dumps. ****** ADDITIONAL INFORMATION ****** I'm attaching the gdb output of 2 core dumps.
Comments:	By: Matthias Nick (mnick) 2010-02-23 15:08:08.000-0600 Hi, I see a lot of "value optimized out" in your backtrace: be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then \'make install\' after enabling, reproduce the crash, and then execute the instructions in doc/backtrace.txt. When complete, attach that file to this issue report. Thanks! By: vieri (vieri) 2010-02-24 03:05:56.000-0600 Thanks but please note that I'm not running 1.4 or 1.6 on this system. It's 1.2. According to the docs, all I need to do is a "make dont-optimize". I just upgraded to 1.2.40 and did a "make dont-optimize". Is there a way to check that "values are not optimized out" before I get a real crash/core dump? (just to save time and to make sure the compiled code is really un-optimized) Is grabbing a "bt full" from "gdb asterisk <processID>" (and looking for "<value optimized out>") enough to show that the currently running asterisk code was compiled with dont-optimize? If I'm 100% sure that asterisk 1.2 was made with "make dont-optimize" but "bt full" still yields "<value optimized out>" then what else can I check? By: David Woolley (davidw) 2010-02-24 05:11:51.000-0600 1.2 hasn't been supported for over a year (except for security fixes). Incidentally, compressing backtraces makes it difficult to have a quick look at them. By: vieri (vieri) 2010-02-24 05:57:19.000-0600 I recompiled 1.2.40 with DONT-OPTIMIZE (correctly). So if it crashes I should get the right info. davidw, I won't compress the gdb output then. Sorry. By the way, if 1.2 is no longer supported, should I still post here if I get another crash? By: Leif Madsen (lmadsen) 2010-03-11 12:43:14.000-0600 As 1.2 is no longer supported except for security fixes, I'd suggest you migrate to 1.4 (or newer), or work around the issue somehow. By: vieri (vieri) 2010-03-12 06:53:18.000-0600 I realize 1.2 is not supported anymore but I'd really appreciate some "pointers" as to what may be failing. It's happening again and I would like to attach a couple of gdb traces so that some charitable soul can lend a hand. By: David Woolley (davidw) 2010-03-12 06:55:43.000-0600 There are forums, mailing lists and IRC channels for doing that. By: vieri (vieri) 2010-03-12 06:58:21.000-0600 All right then. Never mind. Thanks anyway.