grep branch, master, updated. v2.20-91-g83af04c

[Jim Meyering]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "grep".

The branch, master has been updated
       via  83af04cef3139045f1a95a63b70b5935dbf857d8 (commit)
      from  a07a473b558709741ef9a39a97a65ddcedc41eb3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://git.savannah.gnu.org/cgit/grep.git/commit/?id=83af04cef3139045f1a95a63b70b5935dbf857d8


commit 83af04cef3139045f1a95a63b70b5935dbf857d8
Author: Jim Meyering <address@hidden>
Date:   Mon Nov 17 07:54:49 2014 -0800

    tests: big-match: disable OOM-provoking subtest
    
    * tests/big-match: Our application of this regexp '^.*x\(\)\1'
    to a file containing a single matching line of length 2GiB+2
    would cause inordinate memory consumption (over 100GB) via
    regexec.c, but no leak.  That would cause disruption on most
    systems, so remove this subtest.  Reported by Assaf Gordon.

diff --git a/tests/big-match b/tests/big-match
index 20928cf..0da9731 100755
--- a/tests/big-match
+++ b/tests/big-match
@@ -11,7 +11,10 @@ skip_diagnostic=
 
 # These two patterns catch different kinds of
 # failures due to internal integer overflows.
-for pattern in '^.*' '^.*x\(\)\1'; do
+# However, the second one, '^.*x\(\)\1', provokes
+# so much memory consumption via regexec.c that it renders
+# some systems unusable.
+for pattern in '^.*'; do
   diagnostic=$(LC_ALL=C grep -a "$pattern" 2G-plus-2 2>&1 >/dev/null)
   status=$?
 

-----------------------------------------------------------------------

Summary of changes:
 tests/big-match |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
grep