Wrong exception raised when IO.read from a pipe is passed an offset on Windows
When IO.read from a pipe is passed an offset, the expected exception is Errno::ESPIPE, but on Windows Invalid argument (Errno::EINVAL) is raised instead:
C:\Users\Administrator\Desktop>C:\Ruby\ruby-2.2.4-i386-mingw32\bin\ruby.exe -ve "p IO.read('|cmd.exe /C echo hello', 1, 1)" ruby 2.2.4p230 (2015-12-16 revision 53155) [i386-mingw32] The process tried to write to a nonexistent pipe. -e:1:in `read': Invalid argument (Errno::EINVAL) from -e:1:in `<main>'
Updated by jeremyevans0 (Jeremy Evans) over 2 years ago
I think we should fix this to make the behavior on Windows consistent with other operating systems. Attached is a patch that attempts to do so. I'm not sure if the approach the patch takes is the best way to fix this. I also don't have a compilation environment on Windows, so a committer that does should probably check that the patch works.