Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007665OCamlplatform support (windows, cross-compilation, etc)public2017-11-02 19:442017-11-02 19:44
Assigned To 
Platformwin32OSWindows 10 EnterpriseOS Version1511
Product Version4.03.0 
Target VersionFixed in Version 
Summary0007665: with a mix of sockets and non-sockets is not level triggered on Windows
DescriptionI'm using 4.03.0+mingw64 [^] should be "level triggered". That is, as long as a fd is ready, it should be returned. This is opposed to being "edge triggered", where the fd would only be returned when it first becomes ready.

On Windows, with a mixture of sockets and non-sockets does not return all of the ready fds consistently. The first call behaves correctly, but subsequent calls don't.
Steps To ReproduceI uploaded a script which demonstrates the problem, by selecting both a socket and stdin. For some reason, stops reporting the socket as being ready. I ran it on cygwin

$ echo "hello" | ocaml C:/cygwin64/home/glevi/.opam/4.03.0+mingw64c/lib/ocaml/unix.cma
Set up socket

Socket is not yet connected, so only stdin should be ready
stdin is ready
sock is not ready

Connected to socket

Now they both should be ready
stdin is ready
sock is ready

But if we call select again we hit the bug
stdin is ready
sock is not ready

And it repros if we call again
stdin is ready
sock is not ready

Individually stdin is readable: true

Individually sock is readable: true

But together it is still buggy
stdin is ready
sock is not ready
TagsNo tags attached.
Attached Files? file icon [^] (1,674 bytes) 2017-11-02 19:44 [Show Content]

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2017-11-02 19:44 gabelevi New Issue
2017-11-02 19:44 gabelevi File Added:

Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker