The thing is that I'm launching threads, not processes. The message
is printed by runhaskell now that I think about it.
On Nov 16, 2005, at 1:54 AM, Donald Bruce Stewart wrote:
I've been getting this in lambdabot with waitForProcess since 6.4.1 (I
think). Seems harmless though (I think). Try
I think runhaskell reports that when the program has crashed
violently with a segmentation violation.
On Nov 16, 2005, at 1:54 AM, Donald Bruce Stewart wrote:
I've been getting this in lambdabot with waitForProcess since 6.4.1 (I
think). Seems harmless though (I think). Try catching the
On 16 November 2005 11:26, Joel Reymont wrote:
I think runhaskell reports that when the program has crashed
violently with a segmentation violation.
It does, and that's a bug. I fixed it last week.
Cheers,
Simon
On Nov 16, 2005, at 1:54 AM, Donald Bruce Stewart wrote:
I've
Folks,
My program frequently quites (I think) after this message:
waitForProcess: sytem call interrupted
I think it has to do with my killing the thread that calls connectTo,
after a certain timeout. Is there a way to catch this exception so
that the program does not crash?
My code looks
