[asterisk-bugs] [Asterisk 0017472]: parser mangles #include

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17472 
====================================================================== 
Reported By:                seandarcy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17472
Category:                   Core/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.8 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-06-05 10:10 CDT
Last Modified:              2010-06-07 10:37 CDT
====================================================================== 
Summary:                    parser mangles #include
Description: 
With an #include in extensions.conf:

[general]
static=yes
writeprotect=no

#include "exts/extensions-for-fax"

[globals]
TRUNK=DAHDI/g0
TRUNKMSD=1
.............

to a file that exists:

ls -l exts/extensions-for-fax
-rw-r--r--. 1 root root 6157 Nov 13  2009 exts/extensions-for-fax

the parser mangles the #include:

 == Parsing '/etc/asterisk/extensions.conf':   == Found
[Jun  5 10:41:42] ERROR[26393]: config.c:1098 process_text_line: The file
'exts/etensions--for-fax' was listed as a #include but it does not exist.

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

---------------------------------------------------------------------- 
 (0123058) tilghman (administrator) - 2010-06-07 10:37
 https://issues.asterisk.org/view.php?id=17472#c123058 
---------------------------------------------------------------------- 
I think we need you to figure out just exactly what it is about that setup
that causes the problem.  Without the ability to reproduce the problem,
it's difficult for us to track down the issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-07 10:37 tilghman       Note Added: 0123058                          
======================================================================