[asterisk-bugs] [Asterisk 0014474]: Pickup from features

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14474 
====================================================================== 
Reported By:                adriavidal
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14474
Category:                   Resources/res_features
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-02-13 06:08 CST
Last Modified:              2009-02-13 08:59 CST
====================================================================== 
Summary:                    Pickup from features
Description: 
Have just updated our Asterisk 1.4.6 to Asterisk 1.4.23.1 and in every
attempt to use the feature for pickup make a crash on the Asterisk.

Builtin Feature           Default Current
---------------           ------- -------
Pickup                    *8      *


If i use the pickup app everything is OK
_*[23]XX' =>     1, Pickup(${EXTEN:1})    
====================================================================== 

---------------------------------------------------------------------- 
 (0100102) putnopvut (administrator) - 2009-02-13 08:59
 http://bugs.digium.com/view.php?id=14474#c100102 
---------------------------------------------------------------------- 
I don't want to contradict blitzrage, but I have a feeling that the
backtrace that we'd get from this crash would be in the wrong thread, and
that by the time the crash occurs, the offending thread would be in a state
where a backtrace is not useful.

In this particular case, I would recommend describing the situation as
accurately as you can, detailing the call flows, uploading relevant
dialplan portions, and uploading a *full* console trace. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-13 08:59 putnopvut      Note Added: 0100102                          
======================================================================