bug#22793: grep -E assertion failure with back references

2016-02-24 Thread santiagorr
Hi, This is a long standing bug reported to Debian, still present in 2.23. It was forwarded at some point, but I cannot find any reference, so I'm reforwarding it. % echo abc | LANG=C grep -E '(.*)(.*)(.*)\3\2\1' grep: regexec.c:1401: pop_fail_stack: Assertion `num >= 0' failed. More info at: ht

bug#22793: grep -E assertion failure with back references

2016-02-24 Thread Jim Meyering
forcemerge 21513 22793 thanks On Wed, Feb 24, 2016 at 8:18 AM, wrote: > Hi, > > This is a long standing bug reported to Debian, still present in 2.23. > It was forwarded at some point, but I cannot find any reference, so I'm > reforwarding it. > > % echo abc | LANG=C grep -E '(.*)(.*)(.*)\3\2\1'

bug#22793: grep -E assertion failure with back references

2016-02-24 Thread Paul Eggert
With recent 'grep' you can work around the problem by configuring --with-included-regex. That has some other undesirable properties, though. This is really a glibc bug and the glibc patch could be applied to the Debian copy of glibc. Here

bug#22793: grep -E assertion failure with back references

2016-02-24 Thread arnold
Paul Eggert wrote: > With recent 'grep' you can work around the problem by configuring > --with-included-regex. Not so. I did a fresh ./boostrap ./configure --with-included-regex make and it still core dumps: $ echo abc | ./src/grep -E '(.*)(.*)(.*)\3\2\1' grep: rege