[debbugs-tracker] bug#18738: closed (Reference of a uninitialized variable in grep -P)

[GNU bug Tracking System]

Your message dated Wed, 15 Oct 2014 11:51:57 -0700
with message-id <address@hidden>
and subject line Re: bug#18738: Reference of a uninitialized variable in grep -P
has caused the debbugs.gnu.org bug report #18738,
regarding Reference of a uninitialized variable in grep -P
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
18738: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18738
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Reference of a uninitialized variable in grep -P
>
>
>
>
> Date: 
>
> Thu, 16 Oct 2014 00:57:07 +0900
>
>
>
>
> A variable validated_boundary is used in grep -P.  However, it isn't
> initialized correctly.  I found that it causes reference of the
> uninitialized variable and wrong result.
>
>   $ echo . | env LC_ALL=C src/grep -P .
>   $ echo . | env LC_ALL=en_US.utf8 src/grep -P .
>
> We expect that they return each one line, but return each no line.  Their
> test cases are also used to judge whether pcre option is enabled in tests.
> So all tests with pcre option will be skipped by the bug.
>
> Sorry, I have no idea to fix the bug.  BTW, the bug isn't reproduced in
> grep-2.20 or prior.
>
>
>
>
> --- End Message ---

--- Begin Message --- Subject: Re: bug#18738: Reference of a uninitialized variable in grep -P Date: Wed, 15 Oct 2014 11:51:57 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 Thanks for reporting that. It's a bug in one of the optimizations I recently added to work around the libpcre slownesses with UTF-8. It's also a bug in our test cases, which should have caught the bug. I fixed it with the attached patch.

0001-grep-fix-off-by-one-bug-in-P-optimization.patch
Description: Text Data

--- End Message ---