On Saturday, 26 March 2016 at 16:34:34 UTC, Steven Schveighoffer
wrote:
On 3/25/16 6:47 PM, Jonathan Villa wrote:
At this point, I think knowing exactly what input you are
sending would be helpful. Can you attach a file which has the
input that causes the error? Or just paste the input into your
post.
-Steve
I've tested on Debian 4.2 x64 using CHAR type, and it behaves
correctly without any problems.
Clearly this bug must be something related with the Windows
console.
Here's the behaviour in Windows 10 x64:
http://prntscr.com/akskt1
And here's in Debian x64 4.2:
http://prntscr.com/akskjw
JV
