Re: grep 2.5.1: two errors in 'make check'

[Stepan Kasal]

Hello,

On Mon, Feb 03, 2003 at 04:23:54PM -0500, Patrick Smith wrote:
> Stepan Kasal wrote:
> >>    echo - | grep -E -e '(*)b'
> > 
> > This is a change in the way regex interprets this illegal pattern.
> > New regex correctly reports the error:
> 
> Perhaps the test case should be changed to accept either 1 or 2 as the 
> exit code?

grep's included regex will be replaced by the new one soon.
We'll require exit code 2 then.

> >>    echo civic | grep -E -e \
> >>       '^(.?)(.?)(.?)(.?)(.?)(.?)(.?)(.?)(.?).?\9\8\7\6\5\4\3\2\1$'
> >>
> >>expecting exit code 0.  Instead, the exit code is 1, with no output.
> > 
> > This seems to be a bug in current regex code.
> 
> Do the glibc folks know about this?  Or should I report it to them?

I planned to report it.  If you are willing to write the report, I'd be
glad.  If you copy posix/reg* from current GNU libc CVS and compile grep
2.5.1, the resulting grep program doesn't return 1, it simply hangs.

It would be best to write a bug-regex*.c to demonstrate the problem.

I'd be glad if you cc'ed me when sending the bug report.

Thank you very much again,
        Stepan Kasal