Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows error ERROR_NO_DATA should be mapped to EPIPE #4790

Closed
vicuna opened this issue May 14, 2009 · 1 comment
Closed

Windows error ERROR_NO_DATA should be mapped to EPIPE #4790

vicuna opened this issue May 14, 2009 · 1 comment
Labels

Comments

@vicuna
Copy link

vicuna commented May 14, 2009

Original bug ID: 4790
Reporter: vouillon
Status: closed (set by @xavierleroy on 2009-05-19T12:34:56Z)
Resolution: fixed
Priority: normal
Severity: minor
Version: 3.11.0
Fixed in version: 3.11.1+dev
Category: ~DO NOT USE (was: OCaml general)

Bug description

Under Windows, writing to a pipe results in an ERROR_NO_DATA error when the other end of the pipe is closed. This error should therefore be mapped to the EPIPE Unix error (patch attached).

Note that there is an ERROR_BROKEN_PIPE error already mapped to EPIPE, but the error occurs when trying to read from a closed pipe. (Under Unix, the read would simply return 0 to signal an end of file.)

File attachments

@vicuna
Copy link
Author

vicuna commented May 19, 2009

Comment author: @xavierleroy

Thanks for the patch. Applied in 3.11 release branch, will go in release 3.11.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant