Skip to content

Poor error message when openFile fails to open named pipe

openFile cannot open named pipe if no one reads on the other end and fails with particularly unhelpful error message. Quick googling shows that it opens file in non-blocking mode so failure to open is not bug per se, but this fact is not mentioned in documentation.

Example:

  1. Create named pipe
$ mkfifo /tmp/fifo
  1. Now in GHCi:
Prelude> openFile "/tmp/fifo" WriteMode
*** Exception: /tmp/fifo: openFile: does not exist (No such device or address)
Trac metadata
Trac field Value
Version 6.12.3
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component libraries/base
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information