[asterisk-bugs] [Asterisk 0017264]: Crash when using Background() in Macro called by M() option to Dial()

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17264 
====================================================================== 
Reported By:                falves11
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17264
Category:                   Applications/app_dial
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.1.18 
JIRA:                       SWP-1397 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 259958 
Request Review:              
====================================================================== 
Date Submitted:             2010-04-29 17:27 CDT
Last Modified:              2010-05-11 18:28 CDT
====================================================================== 
Summary:                    Crash when using Background() in Macro called by M()
option to Dial()
Description: 
This the section where it blows up.

exten
=>_X.,n,Dial(${CUT(CARRIERLIST,-,${i})},${CUT(TO,-,${i})},M(get-callid^${PROMPT})L(10800000))
;dial once

[macro-get-callid]
exten => s,1,Verbose(2,Playing ${ARG1})
exten => s,n,GotoIf($["${ARG1}" = "0" ]?salida)
exten => s,n,Background(${ARG1})
exten => s,n(salida),MacroExit
====================================================================== 

---------------------------------------------------------------------- 
 (0121758) falves11 (reporter) - 2010-05-11 18:28
 https://issues.asterisk.org/view.php?id=17264#c121758 
---------------------------------------------------------------------- 
I uploaded 3 additional traces, but kindly check the third one, for it may
be a new issue. I just lack the criteria to tell. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-11 18:28 falves11       Note Added: 0121758                          
======================================================================