Hi Max, On Sat, Sep 24, 2011 at 09:56:00PM +0900, Max Bolingbroke wrote: > > It almost certainly was caused by that patch, but the test works OK for me!
Hmm, interesting. > I think I can see what causes this: the output of this new test > depends on the locale of the machine. My locale is en_GB.UTF-8 and and > trying to write a surrogate byte to stdout in this encoding fails with > an exception. Perhaps on your machine you have a Latin 1 locale I don't think so: $ locale LANG=en_GB.UTF-8 LANGUAGE=en_GB:en_US:en_GB:en LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=C LC_TIME=C LC_COLLATE=C LC_MONETARY=C LC_MESSAGES=C LC_PAPER="en_GB.UTF-8" LC_NAME="en_GB.UTF-8" LC_ADDRESS="en_GB.UTF-8" LC_TELEPHONE="en_GB.UTF-8" LC_MEASUREMENT="en_GB.UTF-8" LC_IDENTIFICATION="en_GB.UTF-8" LC_ALL= The testsuite driver will also try to use a UTF8 locale if possible (search for "Try to use UTF8" in testsuite/driver/runtests.py). Thanks Ian _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
