------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1048
Summary: RunGrepTest 62 and 63 fails on s390x
Product: PCRE
Version: 8.11
Platform: Other
OS/Version: Linux
Status: NEW
Severity: bug
Priority: medium
Component: Code
AssignedTo: ph10@???
ReportedBy: ppisar@???
CC: pcre-dev@???
Created an attachment (id=432)
--> (
http://bugs.exim.org/attachment.cgi?id=432)
Build log from RHEL-6 environment
While testing pcre-8.11 on s390x machine with Fedora-14 and RHEL-6 operating
system we encountered problems with pcregrep tests.
We configured sources with --enable-stack-for-recursion and run pcregrep test
62 and 63 terminated with segfault due to small stack (8192 kB). We disabled
the stack recursion and we got unexpected output. Also we get the same strange
output with enabled stack recursion with large enough stack.
The malicious output of the RunGrepTest test is:
Testing pcregrep
pcregrep version 8.11 2010-12-10
--- ./testdata/grepoutput 2010-10-31 13:40:03.000000000 -0400
+++ testtry 2010-12-16 12:42:55.000000000 -0500
@@ -506,25 +506,33 @@
Check up on PATTERN near the end.
RC=0
---------------------------- Test 62 -----------------------------
-pcregrep: pcre_exec() gave error -8 while matching text that starts:
-
This is a file of miscellaneous text that is used as test data for checking
that the pcregrep command is working correctly. The file must be more than 24K
-long so that it needs more than a single read
+long so that it needs more than a single read() call to process it. New
+features should be added at the end, because some of the tests involve the
+output of line numbers, and we don't want these to change.
-pcregrep: Error -8 or -21 means that a resource limit was exceeded.
-pcregrep: Check your regex for nested unlimited loops.
-RC=1
----------------------------- Test 63 -----------------------------
-pcregrep: pcre_exec() gave error -21 while matching text that starts:
+PATTERN at the start of a line.
+In the middle of a line, PATTERN appears.
+This pattern is in lower case.
+
+Here follows a whole lot of stuff that makes the file over 24K long.
+RC=0
+---------------------------- Test 63 -----------------------------
This is a file of miscellaneous text that is used as test data for checking
that the pcregrep command is working correctly. The file must be more than 24K
-long so that it needs more than a single read
+long so that it needs more than a single read() call to process it. New
+features should be added at the end, because some of the tests involve the
+output of line numbers, and we don't want these to change.
+
+PATTERN at the start of a line.
+In the middle of a line, PATTERN appears.
-pcregrep: Error -8 or -21 means that a resource limit was exceeded.
-pcregrep: Check your regex for nested unlimited loops.
-RC=1
+This pattern is in lower case.
+
+Here follows a whole lot of stuff that makes the file over 24K long.
+RC=0
---------------------------- Test 64 ------------------------------
appears
RC=0
FAIL: RunGrepTest
We have: gcc-4.5.1 and glibc-2.12.90.
We got the same results within RHEL-6: gcc-4.4.4 and glibc-2.12.
We will check the bug presence on ppc64 architecture.
We will try to disable all gcc optimization too.
Tests pass on x86_64 or i686 architectures.
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
