[asterisk-bugs] [Asterisk 0012767]: Asterisk crashes when switch => Realtime/@ is specified in the head of a context

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12767 
====================================================================== 
Reported By:                nitzan
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12767
Category:                   Addons/res_config_mysql
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-31-2008 04:15 CDT
Last Modified:              06-01-2008 19:51 CDT
====================================================================== 
Summary:                    Asterisk crashes when switch => Realtime/@ is
specified in the head of a context
Description: 
I'm not sure if this is a known issue or not, but we had to find it the
hard way- we added some "hard" extensions to a context which had switch =>
Realtime/@ before those extensions (we around 20 extensions after the
switch).

It was working perfectly when we had 15 or so extensions, maybe less. But
after adding a few more Asterisk crashed and would not start. Seg Fault all
the way. It kept dying right after the switch and after successfully
loading a couple of post-switch extensions. It almost seems like the switch
and hard config are competing with each other and will work OK as long as
the hard config can "win" and finish before the switch is loaded.
====================================================================== 

---------------------------------------------------------------------- 
 russell - 06-01-08 19:51  
---------------------------------------------------------------------- 
Can you provide the configuration that you used to cause the crash?

Also, can you also provide a backtrace?  To do so, compile Asterisk with
DONT_OPTIMIZE turned on.  Then, start asterisk with the -g option.  After
the crash, there should be a core dump.

# gdb /usr/sbin/asterisk /path/to/core.12345

(gdb) bt
(gdb) bt full 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-01-08 19:51  russell        Note Added: 0087621                          
======================================================================