[kamailio/kamailio] cfg parse error behaviour on a mismatch of #!ifdef/#!endif statements (#2057)
The #!ifdef/#endif statement parsing of the kamailio.cfg does not work correctly on a mismatch of #!ifdef/#!define statements. In some cases will just ignore the #!defines and parses the cfg file without the statements.
version: kamailio 5.3.0-pre0 (x86_64/linux) ed10d7
henning@linux:~/repositories/kamailio/src> ./kamailio -c -f ../etc/test-define.cfg 0(9501) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): parse error in config file /home/henning/repositories/kamailio/src/../etc/test-define.cfg, line 12, column 8: syntax error 0(9501) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): parse error in config file /home/henning/repositories/kamailio/src/../etc/test-define.cfg, line 12, column 8: unknown config variable 0(9501) CRITICAL: <core> [core/cfg.y:3536]: yyerror_at(): parse error in config file /home/henning/repositories/kamailio/src/../etc/test-define.cfg, line 12, column 9-11: ERROR: bad config file (3 errors)
Test cfg to show the problem:
``` henning@linux:~/repositories/kamailio/etc> cat test-define.cfg #!KAMAILIO
#!define foo
#!ifdef foobar1 #!ifdef foobar2 #!endif #!endif #!endif
#!ifdef bar invalid=123 #else children=8 #!endif
request_route { ; }
```
The "bar" condition is parsed, even if the #!define was not set. The WARN message is also not shown in this error case.
Probably the easist fix would be to stop kamailio startup on a mismatch of #!ifdef/#endif statements and output ERROR instead of the current WARN.
While looking at the code I discovered that the index of preprocessor conditions could become negative and even be used for a wrongly placed #!else - I pushed a fix for it: 8f6e826576e52270f21c22a7d94b3026cc22c172 -- this probably needs to be backported.
Otherwise, it is fine for me to stop starting kamailio on a mismatch of ifdef/ifndef-endif pairs.
Thank you Daniel, the example from above works now. Unfortunately the opposite condition still not work:
$./kamailio -c -f ../etc/test-define.cfg -Y /root 0(10801) CRITICAL: <core> [core/cfg.y:3532]: yyerror_at(): parse error in config file /home/henning/repositories/kamailio/src/../etc/test-define.cfg, from line 19, column 2 to line 20, column 0: syntax error ERROR: bad config file (1 errors) 0(10801) WARNING: <core> [core/ppcfg.c:223]: pp_ifdef_level_check(): different number of preprocessor directives: 1 more #!if[n]def as #!endif
``` $ cat test-define.cfg #!KAMAILIO
#!define foo
#!ifdef foobar1 #!ifdef foobar2 #!ifdef foobar3 #!endif #!endif
#!ifdef bar invalid=123 #else children=8 #!endif
request_route { ; } ```
What exactly do you mean by the opposite condition? For the example above I see it fails due to bad config file.
The cfg is invalid, to reproduce it easier. My expectation would be that the config would load fine, as the "bar" condition is not defined at all.
But maybe it is easier to just stop loading the cfg in this mismatch conditions.
In that example, the config is invalid because it is empty, you have 3 ifdefs, then two endifs, so that ifdef bar is all together skipped to the end of the file. The error line is 19, which the end of the file. This case is ok imo.
Ah, I misread the line number. You are right. The backport of 8f6e826 is then only open, I think.
You can backport, if you want. Otherwise I will do it before the next release in the 5.2 series.
Done
Closed #2057.
-
Daniel-Constantin Mierla -
Henning Westerholt