[asterisk-bugs] [Asterisk 0014362]: [patch] Putting a comma in an extension dialpattern causes eventual seg fault
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Feb 2 02:59:46 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14362
======================================================================
Reported By: Nick_Lewis
Assigned To: Corydon76
======================================================================
Project: Asterisk
Issue ID: 14362
Category: Core/PBX
Reproducibility: always
Severity: crash
Priority: normal
Status: ready for testing
Asterisk Version: 1.6.1-beta4
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-01-29 07:25 CST
Last Modified: 2009-02-02 02:59 CST
======================================================================
Summary: [patch] Putting a comma in an extension dialpattern
causes eventual seg fault
Description:
If there is erroneously a comma in an extension dialpattern such as
_9[1-3,5-9].
this leads some time later to a segmentation fault by various *s2=???
assignments in add_exten_to_pattern_tree() of pbx.c
There looks to be a string-unbounded while loop causing it
======================================================================
----------------------------------------------------------------------
(0099207) Nick_Lewis (reporter) - 2009-02-02 02:59
http://bugs.digium.com/view.php?id=14362#c99207
----------------------------------------------------------------------
Re "I'm not sure why it would need to be used within pbx_parseable_goto"
I have not studied the code in detail but in principle if there is a line
in extensions.conf such as
[mycontext]
exten => _123[,]456,1,noop()
and you want to have a goto that jumps to it then it would be something
like
exten => s,n,Goto(mycontext,_123[,]456,1)
Re "square brackets -- something which CANNOT occur within an extension"
The function add_exten_to_pattern_tree() does seem to accept the square
bracket in an extension as long as it is escaped with a backslash.
I fear that we are talking at cross purposes. Can you please give an
example of what you mean
Issue History
Date Modified Username Field Change
======================================================================
2009-02-02 02:59 Nick_Lewis Note Added: 0099207
======================================================================
More information about the asterisk-bugs
mailing list