GNU bug report logs - #15773
grep-2.15 bug report

Previous Next

Package: grep;

Reported by: Mirraz Mirraz <mirraz1 <at> rambler.ru>

Date: Thu, 31 Oct 2013 18:09:01 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


Message #20 received at 15773 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Aharon Robbins <arnold <at> skeeve.com>
Cc: 15773 <at> debbugs.gnu.org, Mirraz Mirraz <mirraz1 <at> rambler.ru>
Subject: Re: bug#15773: grep-2.15 bug report
Date: Fri, 1 Nov 2013 08:15:08 -0700
[Message part 1 (text/plain, inline)]
On Fri, Nov 1, 2013 at 12:53 AM, Aharon Robbins <arnold <at> skeeve.com> wrote:
> Hello All.
>
>> >>> After updating from 2.14 to 2.15 grep has started to fail to match patterns
>> >>> that contain '\s*' or '\s\+'
>>
>> And here's a proper patch, including NEWS and test suite additions:
>
> FWIW, I can't reproduce this in gawk (gawk-4.1-stable branch).
>
> The program below correctly produces no output, with and without the fix
> in dfa.c:lex. (I have added the fix anyway.)
>
> Any ideas why?
>
> Thanks,
>
> Arnold
> ----------------------------------
> BEGIN {
>         pat["^\\s*$"] = pat["^\\s+$"] = pat["^\\s?$"] = pat["^\\s{1}$"] = 1
>         for (i in pat) {
>                 if (" " !~ i) {
>                         printf("pattern \"%s\" failed!\n", i) > "/dev/stderr"
>                         exit 1
>                 }
>         }
>         exit 0
> }

Thanks for the report.
With that, I realized that my new grep test case was inadequate:
it did not force the use of a multibyte locale, and thus did not fail
even without the fix.
I'm amending the patch (not yet pushed) with this:
[k.txt (text/plain, attachment)]

This bug report was last modified 11 years and 135 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.