forked from lix-project/lix
a0e38c16bc
Flex's regexes have an annoying feature: the dot matches everything
except a newline. This causes problems for expressions like:
"${0}\
"
where the backslash-newline combination matches this rule instead of the
intended one mentioned in the comment:
<STRING>\$|\\|\$\\ {
/* This can only occur when we reach EOF, otherwise the above
(...|\$[^\{\"\\]|\\.|\$\\.)+ would have triggered.
This is technically invalid, but we leave the problem to the
parser who fails with exact location. */
return STR;
}
However, the parser actually accepts the resulting token sequence
('"' DOLLAR_CURLY 0 '}' STR '"'), which is a problem because the lexer
rule didn't assign anything to yylval. Ultimately this leads to a crash
when dereferencing a NULL pointer in ExprConcatStrings::bindVars().
The fix does change the syntax of the language in some corner cases
but I think it's only turning previously invalid (or crashing) syntax
to valid syntax. E.g.
"a\
b"
and
''a''\
b''
were previously syntax errors but now both result in "a\nb".
Found by afl-fuzz.
|
||
|---|---|---|
| .. | ||
| primops | ||
| attr-path.cc | ||
| attr-path.hh | ||
| attr-set.cc | ||
| attr-set.hh | ||
| common-eval-args.cc | ||
| common-eval-args.hh | ||
| eval-inline.hh | ||
| eval.cc | ||
| eval.hh | ||
| get-drvs.cc | ||
| get-drvs.hh | ||
| json-to-value.cc | ||
| json-to-value.hh | ||
| lexer.l | ||
| local.mk | ||
| names.cc | ||
| names.hh | ||
| nix-expr.pc.in | ||
| nixexpr.cc | ||
| nixexpr.hh | ||
| parser.y | ||
| primops.cc | ||
| primops.hh | ||
| symbol-table.hh | ||
| value-to-json.cc | ||
| value-to-json.hh | ||
| value-to-xml.cc | ||
| value-to-xml.hh | ||
| value.hh | ||