[asterisk-bugs] [Asterisk 0016053]: Crash on deeply nested while/if statements in AEL

Asterisk Bug Tracker noreply at bugs.digium.com
Tue May 4 16:20:24 CDT 2010


The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16053 
====================================================================== 
Reported By:                diLLec
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16053
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.6 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-11 17:49 CDT
Last Modified:              2010-05-04 16:20 CDT
====================================================================== 
Summary:                    Crash on deeply nested while/if statements in AEL
Description: 
While reloading ael via ael reload the asterisk process runs into SIGSEGV.


This bug is curios since Asterisk starts and loads the ael very well. Also
if ael reload is typed in at the cli when starting Asterisk with -c is
working fine.

The issue only shows up when using asterisk manager or asterisk -r.
====================================================================== 

---------------------------------------------------------------------- 
 (0121378) lmadsen (administrator) - 2010-05-04 16:20
 https://issues.asterisk.org/view.php?id=16053#c121378 
---------------------------------------------------------------------- 
Your backtrace seems to have a lot of <value optimized out> in it.

Please follow the instructions at
http://svn.asterisk.org/svn/asterisk/trunk/doc/backtrace.txt for how to
correctly submit a backtrace. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-04 16:20 lmadsen        Note Added: 0121378                          
2010-05-04 16:20 lmadsen        Status                   new => feedback     
======================================================================




More information about the asterisk-bugs mailing list