aboutsummaryrefslogtreecommitdiffstats
path: root/xcomp/erl-xcomp-arm-linux.conf
diff options
context:
space:
mode:
authorSteve Vinoski <[email protected]>2015-08-10 08:34:28 -0400
committerLukas Larsson <[email protected]>2015-08-18 16:25:28 +0200
commitba8740af39b7d4c612b2ee55e3bad6fbdcaf1418 (patch)
treee04ea41c953fdfb1af6cb0177fc86e6ca3243b9a /xcomp/erl-xcomp-arm-linux.conf
parent61828f77ca2542109ece006d730a4f8fe3300616 (diff)
downloadotp-ba8740af39b7d4c612b2ee55e3bad6fbdcaf1418.tar.gz
otp-ba8740af39b7d4c612b2ee55e3bad6fbdcaf1418.tar.bz2
otp-ba8740af39b7d4c612b2ee55e3bad6fbdcaf1418.zip
Handle ERRNO_BLOCK in fd_driver async functions
Several users on erlang-questions have reported problems with recent releases where output to standard_error causes standard_error_sup to die from receiving an unexpected eagain error. In the fd_driver, change the fd_async() function to handle EINTR, and change fd_ready_async() to handle ERRNO_BLOCK. Add a new test to standard_error_SUITE to generate output to standard_error and ensure that standard_error_sup does not die. Thanks to Kota Uenishi for contributing the test case.
Diffstat (limited to 'xcomp/erl-xcomp-arm-linux.conf')
0 files changed, 0 insertions, 0 deletions