Bug#510219: Info received (Bug#510219: sed: cannot tell if some chars are letters, digits, etc.)

This was bug 9697 in glibc's bugzilla, and is fixed by the patch at git diff 4c2a6f3d 37bdc055ce^ in git://sources.redhat.com/git/glibc.git (gitweb interface at http://repo.or.cz/w/glibc.git). Another regex bug (bug 697 in glibc's bugzilla), by the way, is fixed by the patch at git diff 37bdc055^

Bug#510219: Info received (Bug#510219: sed: cannot tell if some chars are letters, digits, etc.)

On Fri, Jan 09, 2009 at 09:33:45AM +0100, Paolo Bonzini wrote: This was bug 9697 in glibc's bugzilla, and is fixed by the patch at git diff 4c2a6f3d 37bdc055ce^ in git://sources.redhat.com/git/glibc.git (gitweb interface at http://repo.or.cz/w/glibc.git). Another regex bug (bug 697 in

Bug#510219: sed: cannot tell if some chars are letters, digits, etc.

reassign 510219 libc6 quit On Wed, Dec 31, 2008 at 01:58:57PM +0100, Paolo Bonzini wrote: with an usual character. Look at this: ~$ sed 's/a[^a-z]/ax/g' a˚b# correct axb ~$ sed 's/[^a-z]/x/g' a˚b# wrong a˚b I hope this last example helps. Yes, it will help tracking

Bug#510219: sed: cannot tell if some chars are letters, digits, etc.

thomas wrote: 2008/12/30 Paolo Bonzini bonz...@gnu.org: I don't think so, because the bug does not happen with sed from the heirloom toolchest. It probably implements its own regex matcher instead of using libc's. Maybe. But two other GNU programs which probably use libc's regex matcher,

Bug#510219: sed: cannot tell if some chars are letters, digits, etc.

2008/12/31 Paolo Bonzini bonz...@gnu.org: thomas wrote: 2008/12/30 Paolo Bonzini bonz...@gnu.org: I don't think so, because the bug does not happen with sed from the heirloom toolchest. It probably implements its own regex matcher instead of using libc's. Maybe. But two other GNU programs

Bug#510219: sed: cannot tell if some chars are letters, digits, etc.

Something is strange: sed behaves correctly when the pattern begins with an usual character. Look at this: ~$ sed 's/a[^a-z]/ax/g' a˚b# correct axb ~$ sed 's/[^a-z]/x/g' a˚b# wrong a˚b I hope this last example helps. Yes, it will help tracking down the bug (which is in libc,

Bug#510219: sed: cannot tell if some chars are letters, digits, etc.

Package: sed Version: 4.1.5-6 Severity: normal For instance, take U+02E2 MODIFIER LETTER SMALL S: $ echo ˢ | sed -r 's/[a-z]|[^a-z]//' ˢ Expected output: nothing. Sed does not handle “ˢ” (U02E2) as a letter (in [a-z]) nor as a “non-letter” (in [^a-z]). The problem happens with around 3700

Bug#510219: sed: cannot tell if some chars are letters, digits, etc.

Thomas wrote: Package: sed Version: 4.1.5-6 Severity: normal For instance, take U+02E2 MODIFIER LETTER SMALL S: $ echo ˢ | sed -r 's/[a-z]|[^a-z]//' ˢ Expected output: nothing. Sed does not handle “ˢ” (U02E2) as a letter (in [a-z]) nor as a “non-letter” (in [^a-z]). The problem

Bug#510219: sed: cannot tell if some chars are letters, digits, etc.

2008/12/30 Paolo Bonzini bonz...@gnu.org: Thomas wrote: Package: sed Version: 4.1.5-6 Severity: normal For instance, take U+02E2 MODIFIER LETTER SMALL S: $ echo ˢ | sed -r 's/[a-z]|[^a-z]//' ˢ Expected output: nothing. Sed does not handle ˢ (U02E2) as a letter (in [a-z]) nor as a

Bug#510219: sed: cannot tell if some chars are letters, digits, etc.

I don't think so, because the bug does not happen with sed from the heirloom toolchest. It probably implements its own regex matcher instead of using libc's. Paolo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#510219: sed: cannot tell if some chars are letters, digits, etc.

2008/12/30 Paolo Bonzini bonz...@gnu.org: I don't think so, because the bug does not happen with sed from the heirloom toolchest. It probably implements its own regex matcher instead of using libc's. Maybe. But two other GNU programs which probably use libc's regex matcher, bash and grep, do