stdout shouldn't modify binary data on Windows #23303
Labels
area-core-library
SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries.
closed-duplicate
Closed in favor of an existing report
library-io
Currently on Windows, if a List<int> is passed to stdout.add (or stderr.add), any instance of the byte 0xA (an ASCII newline) is replaced by the sequence 0xD 0xA (an ASCII carriage return followed by an ASCII newline). This means that any pure binary data emitted via stdout will be corrupted on Windows. Even when not emitting pure binary data, a subprocess that emits its own \r\n sequences will have an extra \r added if its stdout is piped to the host process's stdout.
The text was updated successfully, but these errors were encountered: