[asterisk-bugs] [Asterisk 0016053]: Crash on deeply nested while/if statements in AEL
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jun 16 10:11:00 CDT 2010
The following issue has been CLOSED
======================================================================
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: closed
Asterisk Version: 1.6.1.6
JIRA: SWP-1414
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: reopened
Fixed in Version:
======================================================================
Date Submitted: 2009-10-11 17:49 CDT
Last Modified: 2010-06-16 10:10 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.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
has duplicate 0017430 segfault in for loop embedded switch st...
======================================================================
----------------------------------------------------------------------
(0123484) murf (manager) - 2010-06-16 10:10
https://issues.asterisk.org/view.php?id=16053#c123484
----------------------------------------------------------------------
I'm closing this bug as "won't fix" because the fix is increase the stack
space for the thread that runs the AEL compiler (in this case). There is no
mech. in Asterisk to create one thread with a different stack size than the
others, and bumping up the size for all threads could end up limiting the
total number of threads that can be created under Asterisk to an
unacceptably low number.
Workarounds are to go ahead and increase the default stack size; or to run
'aelparse -w -d -q' outside Asterisk, and load the resulting
extensions.conf format file via an include in your extensions.conf file.
A more permanent fix would be to allow modules to be loaded with
different stack sizes, but this would be a lot of work, and would really
only benefit a very small number of users!
Issue History
Date Modified Username Field Change
======================================================================
2010-06-16 10:10 murf Note Added: 0123484
2010-06-16 10:10 murf Status feedback => closed
======================================================================
More information about the asterisk-bugs
mailing list