[asterisk-bugs] [Asterisk 0016193]: Segfault with limit data L(x:y) and verbosity >= 3

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16193 
====================================================================== 
Reported By:                asgaroth
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16193
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.26.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-06 04:10 CST
Last Modified:              2009-11-06 13:40 CST
====================================================================== 
Summary:                    Segfault with limit data L(x:y) and verbosity >= 3
Description: 
I am experiencing core dumps when I set a call time limit on for a
call. If I dont use the call time limit option then the dial
application works as expected.

For example, if I have the following dial command:

Dial(SIP/${EXTEN},,L(10800000:60000))

Then I see the following on the console when the dial is executed:

    -- Limit Data for this call:
       > timelimit      = 10800000
       > play_warning   = 60000
       > play_to_caller = yes
       > play_to_callee = no
       > warning_freq   = 0
Segmentation Fault - core dumped

If I remove the time limitation (,L(10800000:60000)) then the dial
works as expected.

If I start asterisk with the
following command:

asterisk -vvvdddgcp

then when on the console I do the following:

"core set verbose 0"
   The dial with limitation works properly

"core ser verbose 1"
   The dial with limitation works properly

"core set verbose 2"
   The dial with limitation works properly

"core set verbose 3"
   The dial with limitation crashes with a segfault

Could this be something to do with writing verbose information to the
console?

====================================================================== 

---------------------------------------------------------------------- 
 (0113334) asgaroth (reporter) - 2009-11-06 13:40
 https://issues.asterisk.org/view.php?id=16193#c113334 
---------------------------------------------------------------------- 
I tried to set the LIMIT_CONNECT_FILE and LIMIT_WARNING_FILE variables
before the dial and the dial command still core dumps when the verbosity is
>= 3.

Here is what I tried in the dialplan:

exten =>
_NX.,1,Set(LIMIT_CONNECT_FILE=tt-monkeys.gsm,LIMIT_WARNING_FILE=tt-monkeys.gsm)
exten => _NX.,n,Verbose(${LIMIT_CONNECT_FILE})
exten => _NX.,n,Dial(SIP/003531${EXTEN}@magratheagw,,${CallTimeLimit})

When attempting the dial, here is what is on the console:

    -- Executing [8262900 at magratheaout:1]
Set("SIP/bruce.mcalister0-0840e0b8",
"LIMIT_CONNECT_FILE=tt-monkeys.gsm|LIMIT_WARNING_FILE=tt-monkeys.gsm") in
new stack
[Nov  6 19:31:19] WARNING[13463]: pbx.c:5936 pbx_builtin_setvar: Setting
multiple variables at once within Set is deprecated.  Please separate each
name/value pair into its own line.
    -- Executing [8262900 at magratheaout:2]
Verbose("SIP/bruce.mcalister0-0840e0b8", "tt-monkeys.gsm") in new stack
tt-monkeys.gsm
    -- Executing [8262900 at magratheaout:3]
Dial("SIP/bruce.mcalister0-0840e0b8",
"SIP/0035318262900 at magratheagw||L(10800000:60000)") in new stack
    -- Limit Data for this call:
       > timelimit      = 10800000
       > play_warning   = 60000
       > play_to_caller = yes
       > play_to_callee = no
       > warning_freq   = 0
Segmentation Fault - core dumped 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-06 13:40 asgaroth       Note Added: 0113334                          
======================================================================