With bad UTF-8, cygwin can create files it can't read

[Corinna Vinschen]

On Mar 25 14:34, Kyzer wrote:
> Hello,
> 
> I've found that if you use cygwin to create a file with badly-encoded
> UTF-8, readdir() gives out an entry with a name that cygwin won't
> subsequently accept.
> 
> * create a file using filename with hex bytes F4 8F BF BF
> * readdir() reports the filename as hex bytes E2 8E B3 ED BF BF
> * attempting to open or unlink the filename E2 8E B3 ED BF BF fails
> * attempting to open or unlink the filename F4 8F BF BF succeeds

Thanks for the testcase.  I'll have a look later this week (I hope).


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20150330/47cde0af/attachment.sig>