[ sorry Michael's message appears to have been stuck in a time-warp: it got
accidentally caught by the filter on haskell.org and I don't check the
bounced mail as often as I should... ]
> > This bug is quite annoying, because it makes all ghc
> compiled programs
> > unsuitable for normal usage (
On Mon, Dec 06, 1999 at 11:34:22 +0900, Manuel M. T. Chakravarty wrote:
> Moin GHC Hackers,
>
> I think there is still a problem with non-blocking I/O hosing some shells
> on abnormal program termination. This is on Linux, using bash and the
> latest sources from CVS.
[...]
> This bug is quite a
> I think there is still a problem with non-blocking I/O
> hosing some shells on abnormal program termination. This is
> on Linux, using bash and the latest sources from CVS.
Yep, you're probably right. I think I'm going to back off on this one and
not set the non-blocking flag on stdout and s
Simon Marlow <[EMAIL PROTECTED]> wrote,
> > I think there is still a problem with non-blocking I/O
> > hosing some shells on abnormal program termination. This is
> > on Linux, using bash and the latest sources from CVS.
>
> Yep, you're probably right. I think I'm going to back off on this on
Michael and I worked out a way for coping with this phenomenon while it lasts,
(even if this is now fixed for most cases except interruption, I still haven't
managed to get a new ghc going due to the CVS woes :|),
so if anyone is interested, instructions follow:
Write yourself a small C-program wh
