GNU bug report logs - #22181
endless loop in grep 2.22

Previous Next

Full log

View this message in rfc822 format

From: Jim Meyering <jim <at> meyering.net>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: Christian Boltz <grep-bug <at> cboltz.de>, 22181 <at> debbugs.gnu.org, Seth Arnold <seth.arnold <at> canonical.com>
Subject: bug#22181: endless loop in grep 2.22
Date: Fri, 8 Jan 2016 17:01:45 -0800

[Message part 1 (text/plain, inline)]

On Fri, Jan 8, 2016 at 1:32 PM, Jim Meyering <jim <at> meyering.net> wrote:
> On Fri, Jan 8, 2016 at 8:50 AM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
>> On 01/07/2016 09:47 PM, Jim Meyering wrote:
>>>
>>> FAIL: encoding-error
>>> ====================
>>> ...
>>> --- exp 2016-01-07 21:39:42.018646618 -0800
>>> +++ out 2016-01-07 21:39:42.018646618 -0800
>>> @@ -1 +1 @@
>>> -Binary file in matches
>>> +Pedro P\xe9rez
>>> + fail=1
>>
>>
>> I can't reproduce that in Fedora 23 x86-64, which is using gcc 5.3.1
>> 20151207 (Red Hat 5.3.1-2).
>>
>> One hypothetical explanation is a bug or incompatibility in the
>> bleeding-edge Debian shell, which I suppose could cause
>> require_en_utf8_locale_ to do the wrong thing (i.e., to fail to report that
>> the en_US.UTF-8 locale is missing). You might check the output of the
>> command './get-mb-cur-max en_US.UTF-8' when you have the time.
>
> Will investigate. In the mean time, here's a patch for the
> false-positive failure I mentioned:

It was trivial: printf does not necessarily support \xHH hexadecimal
escapes. I switched the input generation to use printf with an octal
escaped byte instead, and now it works.

I've just pushed the attached along with the preceding patch.

[0001-tests-fix-encoding-error-test-failure-to-use-of-prin.patch (text/x-patch, attachment)]

Previous Next

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