On 4/30/2010 10:44 AM, Andrew Sullivan wrote:
> On Fri, Apr 30, 2010 at 09:49:20AM -0400, Andrew Sullivan wrote:
>> I'd look for this too, but note that 0xac is one byte of one of the
>> Unicode encodings of the Euro symbol.  Given there've been two reports
>> of this, I'd also start to have a look for different Unicode versions.
>> There might be a library problem here.
> 
> Digging a little more at the Unicode tables, I also note that this is
> the ISO 8859-1 and Win CP 1257 encoding for NOT SIGN.  The Unicode
> encoding for this is one of {0x000000AC || 0x00AC || 0xC2 0xAC}
> depending on the encoding scheme.  Any chance one of the machines
> involved in these reports is a Windows machine?  Could this be due to
> the native UTF-16 vs. native UTF-8 issue?

Right now it looks more like a dangling pointer issue, which behaves 
different depending on OS and libc version.


Jan

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin