Re: thread blocked indefinitely

"Simon Marlow" <simonmar@xxxxxxxxxxxxx> writes:

> > I'm now `GHC.Conc.forkProcess`ing only from the initial 
> > thread, and all   
> > seems well.  Thanks for the suggestion!
> >  
> > Any idea when `forkProcess` might get fixed?  Don't hurry on my
> > account; I'm just curious.
> 
> There's a comment in the code from Sigbjorn who tried to fix it and was
> unsuccessful, so it's probably a non-trivial fix.  I'll take a look next
> time I'm in the area, unless it's a complete show-stopper for anyone.
> 
> Cheers,
>       Simon

I was just reading through old e-mail and saw this.  The state of
affairs described here sounds like a nasty bug waiting to bite.

Would it be better to change forkProcess to detect whether it's being
called from the initial thread, and give some sort of error ("GHC
internal error: forkProcess must only be called from the initial
thread") if not?

Carl Witty