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

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Nov 20 06:27:37 CST 2009


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-20 06:27 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?

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

---------------------------------------------------------------------- 
 (0114032) snuffy (manager) - 2009-11-20 06:27
 https://issues.asterisk.org/view.php?id=16193#c114032 
---------------------------------------------------------------------- 
This is most likely another place where we are strlen() on a null string.
One of these was fixed not too long ago using 'S_OR()' for a printf.

Technically i think opensolaris now has null checks on strlen/printfs in
later rev past 111b. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-20 06:27 snuffy         Note Added: 0114032                          
======================================================================




More information about the asterisk-bugs mailing list