decodingerror002 failure

[Daniel Fischer]

On Tuesday 27 September 2011, 08:35:26, Max Bolingbroke wrote:
> On 26 September 2011 23:30, Daniel Fischer
> 
> <daniel.is.fischer at googlemail.com> wrote:
> > In hex, the error sequences are
> > common: EF BF BD
> > expected: C8
> > actual: ED B3 88
> 
> It looks like your iconv has erroneously UTF-8 encoded the lone
> surrogate codepoint 0xDCC8 to UTF-8.

Hm, where does iconv come into play? That's the byte I see between 0A and 
4C (\n and L) when I open decodingerror.stdout in a hex editor, read it in 
via ByteString or openBinaryFile, in an untouched repo. And that's the lone 
byte in decodingerror002.in.
So the only opportunity for iconv to have a part in this would be during 
git cloning, wouldn't it? Does git use iconv when cloning?

> This is in violation of the
> recommendations of the UTF standard.
> 
> What version of which iconv are you linking against?

$ iconv --version
iconv (GNU libc) 2.11.3
Copyright © 2009 Free Software Foundation, Inc.
Dies ist freie Software; in den Quellen befinden sich die 
Lizenzbedingungen.
Es gibt KEINERLEI Garantie; nicht einmal für die TAUGLICHKEIT oder
VERWENDBARKEIT FÜR EINEN ANGEGEBENEN ZWECK.
Implementiert von Ulrich Drepper.

No libiconv in the linux partitions, config.log contains
ICONV_INCLUDE_DIRS=''
ICONV_LIB_DIRS=''

so I guess I'm not linking against any iconv.