bug#21763: poor performance since grep 2.19 when comparing files with grep

2015-10-27 Thread Bennett, Steve
> Thank you for reporting that. > Interesting: that progression (time vs. increasing N) is clearly quadratic > or worse when using a multibyte locale, but is linear with LC_ALL=C. > I suspect when you run "locale", it reports something like en_US.utf8. Yes, it's a UTF8 locale. I hadn't thought of

bug#21755: new snapshot available: grep-2.21.82-fbc5

2015-10-27 Thread Paul Eggert
Bruce Dubbs wrote: ( ulimit -s 50; LC_ALL=C src/grep -P -n '^([/](?!/)|[^/])*~/.*' pcrejit.txt ) but changing to a ulimit of 40 KB, it consistently segfaults. That also jibes with what valgrind --tool=massif --stacks=yes reports. $ valgrind --tool=massif --stacks=yes ./grep -P -n '^([/](?!/

bug#21755: new snapshot available: grep-2.21.82-fbc5

2015-10-27 Thread Bruce Dubbs
Paul Eggert wrote: Bruce Dubbs wrote: ( ulimit -s 50; LC_ALL=C src/grep -P -n '^([/](?!/)|[^/])*~/.*' pcrejit.txt ) but changing to a ulimit of 40 KB, it consistently segfaults. That also jibes with what valgrind --tool=massif --stacks=yes reports. $ valgrind --tool=massif --stacks=yes ./g

bug#21670: surprising bug in grep -e with anchors

2015-10-27 Thread Jim Meyering
On Sun, Oct 11, 2015 at 2:01 PM, greg boyd wrote: > This bug appears in GNU grep version 2.20. It is not present in the older > version I have installed on a home system (2.6.3.) > > test case (single line) > abchelloabc > > grep does not find the line with grep -e '^hello' nor with grep -e 'hell