If the MVar was set up prior to the fork, I can imagine things going crazy trying to use it on the ther side of the fork - especially if their were waiting readers or writers while the fork was executing. On Jul 14, 2012 3:01 PM, "Joey Hess" <j...@kitenet.net> wrote:
> I've isolated the hang further to hPipeFrom's use of System.Log.Logger. > Commenting out calls to logging functions makes it reliably run ok. See > the "LINE OF DEATH" in the attached updated test case. > > ... And it turns out that System.Log.Logger uses a MVar to hold the > logger information. So I think this points to a MissingH bug, although I > don't yet understand it. > > -- > see shy jo >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
