Bug #12230: Wrong exception raised when IO.read from a pipe is passed an offset on Windows

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 2.2.4p230 (2015-12-16 revision 53155) [i386-mingw32]
• Backport: 2.4: REQUIRED, 2.5: REQUIRED, 2.6: REQUIRED

[vais (Vais Salikhov)]

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>'

[jeremyevans0 (Jeremy Evans)]

• File win32-seek-espipe.patch win32-seek-espipe.patch added

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.

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

Applied in changeset git|0a63c4d5fbbbfae9aba92c78e39b1521b90f1b06.

---

Fix errno at seeking socket/pipe on Windows

[Bug #12230]

[nobu (Nobuyoshi Nakada)]

• Related to Bug #15199: scanf.rb broken with io from IO.pipe (MinGW or Windows?) added

[nobu (Nobuyoshi Nakada)]

• Backport changed from 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN to 2.4: REQUIRED, 2.5: REQUIRED, 2.6: REQUIRED