[debbugs-tracker] bug#21273: closed ([PATCH] grep: avoid use of uninitialized variable)

[GNU bug Tracking System]

Your message dated Wed, 19 Aug 2015 17:00:41 -0700
with message-id <address@hidden>
and subject line Re: bug#21273: [PATCH] grep: avoid use of uninitialized 
variable
has caused the debbugs.gnu.org bug report #21273,
regarding [PATCH] grep: avoid use of uninitialized variable
to be marked as done.

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


-- 
21273: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21273
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [PATCH] grep: avoid use of uninitialized variable Date: Sun, 16 Aug 2015 11:17:52 +0900

Uninitialized value of variable BACKREF is referred in EGexecute.  It
does not cause wrong result, but regex may be used even when it is not
needed.  It may lead grep to slowdown.

By the way, gawk initializes the variable already, so it does not have
to be fixed.

0001-grep-avoid-use-of-uninitialized-variable.patch
Description: Text document

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#21273: [PATCH] grep: avoid use of uninitialized variable
>
>
>
>
> Date: 
>
> Wed, 19 Aug 2015 17:00:41 -0700
>
>
>
>
> On Sat, Aug 15, 2015 at 7:17 PM, Norihiro Tanaka <address@hidden> wrote:
> > Uninitialized value of variable BACKREF is referred in EGexecute.  It
> > does not cause wrong result, but regex may be used even when it is not
> > needed.  It may lead grep to slowdown.
> >
> > By the way, gawk initializes the variable already, so it does not have
> > to be fixed.
>
> Thank you for that fix. I have determined that the problem was
> introduced since the latest release, so this does not require a
> NEWS entry, then added that info and a paraphrasing of your
> comment above to the commit log. Pushed here:
>
>   http://git.savannah.gnu.org/cgit/grep.git/commit/?id=8a33cdeba4ba0
>
>
> --- End Message ---