[asterisk-bugs] [Asterisk 0016889]: Asterisk 1.2.39 core dump

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16889 
====================================================================== 
Reported By:                vieri
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16889
Category:                   Core/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.2.X 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-23 12:12 CST
Last Modified:              2010-02-24 03:05 CST
====================================================================== 
Summary:                    Asterisk 1.2.39 core dump
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.

====================================================================== 

---------------------------------------------------------------------- 
 (0118440) vieri (reporter) - 2010-02-24 03:05
 https://issues.asterisk.org/view.php?id=16889#c118440 
---------------------------------------------------------------------- 
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? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-24 03:05 vieri          Note Added: 0118440                          
======================================================================