On Dez 22 2019, Paul Eggert wrote:
> As Bug#21513 is now fixed both in Gnulib (which grep uses when configured
> --with-included-regex) and in Glibc (which grep uses when configured
> --without-included-regex) I am marking the bug report as done.
tests/triple-backref now runs forever.
Andreas.
As Bug#21513 is now fixed both in Gnulib (which grep uses when configured
--with-included-regex) and in Glibc (which grep uses when configured
--without-included-regex) I am marking the bug report as done.
Paul Eggert wrote:
It's a bug in the glibc regular expression matcher,
and as such will need a glibc fix. I plan to propose a patch there.
I created glibc bug report BZ#18986 about this, and put in a pointer to the
Gnulib patch. Hope that's enough to get it fixed in glibc, eventually.
http
Thanks for reporting that. It's a bug in the glibc regular expression matcher,
and as such will need a glibc fix. I plan to propose a patch there. In the
meantime I fixed the Gnulib replacement for the matcher, here:
http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=5513b40999149090987a
Hi,
This command
grep -E '0|()0|\1|0'
will cause an assert error:
grep: regexec.c:1401: pop_fail_stack: Assertion `num >= 0' failed.
Happens both in the latest release (2.21) and the latest git code.
(this was found with american fuzzy lop)
cu,
--
Hanno Böck
http://hboeck.de/
mail/jabber: ha
