summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJim Meyering <meyering@fb.com>2014-11-17 07:54:49 -0800
committerJim Meyering <meyering@fb.com>2014-11-17 07:54:49 -0800
commit83af04cef3139045f1a95a63b70b5935dbf857d8 (patch)
treeaeca922d30ce14040c26a175d62fc6bc1398c200
parenta07a473b558709741ef9a39a97a65ddcedc41eb3 (diff)
downloadgrep-83af04cef3139045f1a95a63b70b5935dbf857d8.tar.gz
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.
-rwxr-xr-xtests/big-match5
1 files changed, 4 insertions, 1 deletions
diff --git a/tests/big-match b/tests/big-match
index 20928cf7..0da97316 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=$?