aboutsummaryrefslogtreecommitdiffstats
path: root/.gitattributes
diff options
context:
space:
mode:
authorJohn Högberg <[email protected]>2019-05-07 11:39:34 +0200
committerJohn Högberg <[email protected]>2019-05-07 14:22:36 +0200
commit4df8cf1f67a12d2c730e85ab4de64b6fd7557050 (patch)
treeb737b8be2a5c913f2a4766b34a7c23ab7ae3a986 /.gitattributes
parent0e10a805bde0f1ce8ba9282660aaa2fd1e01fc81 (diff)
downloadotp-4df8cf1f67a12d2c730e85ab4de64b6fd7557050.tar.gz
otp-4df8cf1f67a12d2c730e85ab4de64b6fd7557050.tar.bz2
otp-4df8cf1f67a12d2c730e85ab4de64b6fd7557050.zip
kernel: Force synchronous port_commands in user/user_drv
Banging data to a local port was always synchronous prior to Erlang/OTP R16, and these modules relied on that behavior to report that data had successfully been enqueued on the stdout port. This would cause data to be silently dropped if the command didn't run synchronously and the emulator halted before the port received the data. This was fairly rare in practice, but could be seen from time to time on Windows with escripts that ended with a call to io:format/2, such as the one used by the escript_SUITE:create_and_extract test. This is a minimal band-aid to make things reliable again. A more complete fix would add explicit synchronization with the port.
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions