aboutsummaryrefslogtreecommitdiff
path: root/tests/lang/eval-okay-backslash-newline-1.nix
diff options
context:
space:
mode:
authorTuomas Tynkkynen <tuomas@tuxera.com>2018-02-25 23:51:47 +0200
committerTuomas Tynkkynen <tuomas@tuxera.com>2018-03-02 17:30:48 +0200
commita0e38c16bc7773d0fc62771a9935e079c00899ef (patch)
tree9f30fc3be4c4be6742d220a1b0363be8f053d383 /tests/lang/eval-okay-backslash-newline-1.nix
parent939cf4ccebb199e61da648873fb078ae8833263f (diff)
libexpr: Recognize newline in more places in lexer
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.
Diffstat (limited to 'tests/lang/eval-okay-backslash-newline-1.nix')
-rw-r--r--tests/lang/eval-okay-backslash-newline-1.nix2
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/lang/eval-okay-backslash-newline-1.nix b/tests/lang/eval-okay-backslash-newline-1.nix
new file mode 100644
index 000000000..7fef3dddd
--- /dev/null
+++ b/tests/lang/eval-okay-backslash-newline-1.nix
@@ -0,0 +1,2 @@
+"a\
+b"