Simon Marlow wrote (snipped):
The thread reading from the handle has a lock on it, so that hClose has
to wait before it can gain access to the handle to close it.
OK, so it isn't a bug but expected behaviour that if you have one thread
doing hGetChar on a handle, an attempt to close the handle in
> I have a problem with a handle for which hClose does not
> terminate. Unfortunately
> it's too much work for me to narrow it down now, but perhaps
> it can be worked out
> from these facts?
> (1) it's a socket connection.
> (2) it has BlockBuffering (Just 4096) set.
> (3) it is possible that
I have a problem with a handle for which hClose does not terminate. Unfortunately
it's too much work for me to narrow it down now, but perhaps it can be worked out
from these facts?
(1) it's a socket connection.
(2) it has BlockBuffering (Just 4096) set.
(3) it is possible that another thread is s
