#10736: threadWaitRead/registerFd unusable -------------------------------------+------------------------------------- Reporter: mboes | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.10.2 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Revisions: -------------------------------------+------------------------------------- Comment (by bgamari): What operating system is this on? The trouble is that the behavior of the functions backing the event manager are a bit platform-specific (in this way, it's a bit of a leaky abstraction, although I'm not sure we can do much better). Moreover, the platforms' documentation in this area tends to be quite poor, even in the case of Linux. In this particular case, you are running into the fact that `epoll` is [http://stackoverflow.com/questions/8057892/epoll-on-regular-files not] [http://stackoverflow.com/questions/8645721/why-does-select-select-work- with-disk-files-but-not-epoll?lq=1 supported] on regular files (the fact that this answer refers to the kernel's `eventpoll.c` for a definitive answer is an indication of just how lacking the documentation is in this area). I would like to improve the documentation for the event manager interfaces, but it require time to sort out where the relevant information can be found in the various platform documentation sources. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10736#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler