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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
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:                     new
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 12:58 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0121350) diLLec (reporter) - 2010-05-04 12:58
 https://issues.asterisk.org/view.php?id=16053#c121350 
---------------------------------------------------------------------- 
Sorry, just noted that I've commented the 13th level out in
extensions.ael-2010-05-04. I've attached extensions.ael-2010-05-04_depth13
which does the job.

Further please note that you can't reproduce the issue if you are using 

asterisk -cvvvvvvvv

with a following 'ael reload'. The way I've been able to reproduce it is
when asterisk is already started and you connect on a seperate thread with


asterisk -rvvvvvv

and then issue 'ael reload'. Please remember that starting asterisk with
that configuration is no problem! 

Following that, getting a backtrace from the process after SIGSEG is
thrown needs to be done by executing:

gdb /usr/sbin/asterisk
(gdb) run -cvvvvvvvvv
... 

on the first terminal session. After that you connect to asterisk via

asterisk -rvvvvvvvvvv

and start 'ael reload'.

You should then see the SIGSEGV in gdb and be able to call the BT for it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-04 12:58 diLLec         Note Added: 0121350                          
======================================================================