[asterisk-bugs] [Asterisk 0013046]: Asterisk segfault at startup/ael reload

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13046 
====================================================================== 
Reported By:                bootc
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   13046
Category:                   PBX/pbx_ael
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.21 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-07-10 04:14 CDT
Last Modified:              2009-02-13 13:04 CST
====================================================================== 
Summary:                    Asterisk segfault at startup/ael reload
Description: 
I have a reasonably large and complex dialplan, and after I added a switch
statement pbx_ael started crashing most of the time (but not always) after
an "ael reload" command, or on startup when loading the dialplan.
====================================================================== 

---------------------------------------------------------------------- 
 (0100117) murf (administrator) - 2009-02-13 13:04
 http://bugs.digium.com/view.php?id=13046#c100117 
---------------------------------------------------------------------- 
I've just gone over the flex-generated source we are publishing, and while
I see a fair amount of pointer arithmetic, I was not able to find any
instances of where any int was cast to a pointer or vice-versa. I did see
some comparisons between a size_t and an int, but I've never it given it
any thought, as the compiler (gcc) seems to handle it just fine. Recently,
while compiling stuff usually not compiled into asterisk by default, I
found some void ptr <=> int and size_t <=> void* type issues, which the
compiler pointed out, which I fixed and committed. We have an automated
build farm that is a mix of linux and freebsd, 32 and 64 bit, and if
there's going to be issues, they usually get highlighted there.

I have noted that ael loads are not locked, and doing two loads at once
can lead to problems, but I haven't gotten around to addressing that yet.
Could this be an issue for you? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-13 13:04 murf           Note Added: 0100117                          
======================================================================