GNU bug report logs -
#29446
GNU grep 3.1 fails test suite when PCRE lacks JIT
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Wed, 9 Sep 2020 16:10:41 -0700
with message-id <5878c1f6-3f5c-f663-4276-d8eece95fe1d <at> cs.ucla.edu>
and subject line Re: GNU grep 3.1 fails test suite when PCRE lacks JIT
has caused the debbugs.gnu.org bug report #29446,
regarding GNU grep 3.1 fails test suite when PCRE lacks JIT
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
29446: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29446
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi there grep developers,
I'm trying to package GNU grep 3.1 on 64-bit PowerPC (big-endian) for
our Linux distribution, Adélie Linux. It seems to be working quite
well, except there is a failing test: pcre-jitstack.
"grep: internal PCRE error: -21" (which is PCRE_ERROR_RECURSIONLIMIT)
is printed. I believe that this is because we have to disable JIT on
the ppc64 platform (because the JIT compiler is badly broken on it).
I am not very familiar with either of the grep or PCRE codebases so I
am not sure exactly how to best skip the test when PCRE does not have
JIT support enabled. Otherwise, I would have included a patch.
Thank you for your time.
Best regards,
- --arw
- --
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJaGeIDAAoJEMspy1GSK50UYKoP/3xmewMMArDgld6jvXdpFEdG
GQeRly0BWxckUksE3FNRdfw9OBS2VAJKd8FpU+3wbRBp0Lnf9btTBGiHD9vB0cBX
kRQIADw87M6uDIBKedN1lGMjr9E8BcLOj/5GTRIvd6eKDVZspVRW7bHGdb+n4om4
uVlmpyP2niSfYkcE/F9Bv0BQrjjyHUXKbKP+u7O3nA/VJt27tOM1RuIQSnKE2sLE
9hOd8YY88zPP8xAXpSccvq1qnbsCH+X8Av/nzyMGc/xdcvlkbepweeLWZ9eF0+x8
oqBE/fg7EQ4VawUpCTlgwD7+K2c+pXvXIkhksxxNgq6YP1UccCiz8T6JDZsq6VAY
RU4MdlxRrKWMKjVf+GQXBR0tr+F+LeOT9QXC6+vlqISjoT2Ev9NM2HIUamii5uBU
I+9q3Yc8mw2adL07kiMCtKRCMVSoa5Qx+lNaMIsSGCYLOzNajZr/IjzZjbMKSTbC
jb2yx/c6zTshghl1+g/OJYyEikia8T4qXnLp7LwRgF5INp2ep+4rFGk3N5K8SD8X
Xg2vh6QQTqORQChGRHMI9fTWvj5zrxboSCFqinK7ASCZO3uRE/AGvkJcmO+LPPz8
ZPSksPvHvHZCZ76Wq1R8Fo3PAcOPtX4YCEUyNwMb4aOlNORZohFdaZJIMmTdkq9p
r1GLLYi8RjC6V3zaCDw7
=Of5f
-----END PGP SIGNATURE-----
[Message part 3 (message/rfc822, inline)]
[Message part 4 (text/plain, inline)]
On 1/2/20 1:47 PM, Thomas Deutschmann wrote:
> I managed to reproduce the error using pure Debian:
Thanks, with that recipe I reproduced the problem on Ubuntu 18.04.5, and
installed the attached. I'll boldly close the bug report.
libpcre is quite a pain to use, and makes 'grep' less reliable. Perhaps somebody
with some time could see whether libpcre2 is any better.
[0001-grep-fix-PCRE-JIT-test-when-JIT-not-available.patch (text/x-patch, attachment)]
[0002-grep-fix-logic-for-growing-PCRE-JIT-stack.patch (text/x-patch, attachment)]
This bug report was last modified 4 years and 313 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.