GNU bug report logs - #23234
unexpected results with charset handling in GNU grep 2.23

Previous Next

Full log

Message #40 received at 23234-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Eric Blake <eblake <at> redhat.com>, Björn JACKE
 <bjoern <at> j3e.de>, 23234-done <at> debbugs.gnu.org
Subject: Re: bug#23234: unexpected results with charset handling in GNU grep
 2.23
Date: Sun, 10 Apr 2016 01:43:10 -0700

[Message part 1 (text/plain, inline)]

Paul Eggert wrote:
> I plan to change GNU grep to use this new facility, and to add some grep test
> cases for this issue.

I did that by installing the attached patches into the grep master. This fixes 
the bug for me, so I'm closing the bug report.

These patches mostly just report the fix and add test cases. The actual fix was 
in gnulib, here:

http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=b7bc3c1a4e78add4cbad39ae1a0c4fb0747b483f

This gnulib fix works around the underyling glibc facility which caused the 
problem, for which I've filed a bug report here:

https://sourceware.org/bugzilla/show_bug.cgi?id=19932

It's not clear when the glibc bug will be fixed. Until it is, one should expect 
similar problems to crop up in applications other than 'grep'.

[0001-build-update-gnulib-submodule-to-latest.txt (text/plain, attachment)]

[0002-grep-in-C-locale-all-bytes-are-valid-characters.txt (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.