[asterisk-bugs] [Asterisk 0012486]: Segfault when using realtime queues and 'strategy' is not NULL

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12486 
====================================================================== 
Reported By:                bcnit
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12486
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0-beta7.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-21-2008 11:42 CDT
Last Modified:              04-23-2008 03:08 CDT
====================================================================== 
Summary:                    Segfault when using realtime queues and 'strategy'
is not NULL
Description: 
Using realtime, a queue is defined in a MySQL database as:

----------------------------------
CREATE TABLE IF NOT EXISTS `queues` (
  `name` varchar(128) NOT NULL,
  `strategy` varchar(128),
  PRIMARY KEY  (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
----------------------------------

If a record is created the 'strategy' field is not NULL, Asterisk
segfaults when any action takes place on that queue. These actions include
'queue show QUEUENAME' at the CLI or using the Queue(QUEUENAME) application
within the dialplan.
====================================================================== 

---------------------------------------------------------------------- 
 bcnit - 04-23-08 03:08  
---------------------------------------------------------------------- 
Yes, it's OK. Sorry about the dup. I did search, honest!! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-23-08 03:08  bcnit          Note Added: 0085877                          
======================================================================