grep: "grep '\)'" reports an error again

* src/grep.c (try_fgrep_pattern): With -G, pass \) through to
GEAcompile so that it can complain.  This fixes an unexpected
change in behavior from grep 3.4 and earlier.
* tests/filename-lineno.pl: Add tests for this sort of thing.

1 files changed, 16 insertions, 0 deletions

diff --git a/tests/filename-lineno.pl b/tests/filename-lineno.pl
index 8940b1c7..ebd8d1ec 100755
--- a/tests/filename-lineno.pl
+++ b/tests/filename-lineno.pl
@@ -87,6 +87,22 @@ my @Tests =
     $err_subst,
     {ERR => "$prog: Unmatched [...\n" x 2},
    ],
+
+   # Test unmatched ) as well.  It is OK with -E and an error with -G and -P.
+   ['invalid-re-E-paren', '-E ")"', {IN=>''}, {EXIT=>1}],
+   ['invalid-re-E-star-paren', '-E ".*)"', {IN=>''}, {EXIT=>1}],
+   ['invalid-re-G-paren', '-G "\\)"', {EXIT=>2},
+    {ERR => "$prog: Unmatched ) or \\)\n"},
+   ],
+   ['invalid-re-G-star-paren', '-G "a.*\\)"', {EXIT=>2},
+    {ERR => "$prog: Unmatched ) or \\)\n"},
+   ],
+   ['invalid-re-P-paren', '-P ")"', {EXIT=>2},
+    {ERR => "$prog: unmatched parentheses\n"},
+   ],
+   ['invalid-re-P-star-paren', '-P "a.*)"', {EXIT=>2},
+    {ERR => "$prog: unmatched parentheses\n"},
+   ],
   );
 
 my $save_temps = $ENV{DEBUG};