unfortunately I forgot to ask my questions ;o)
What does heapCensus mean ?
It's an internal error in GHC's heap profiler, and indicates a bug
somewhere. Could you send us the code?
Cheers,
Simon
___
Glasgow-haskell-users mailing list
Hi again,
unfortunately I forgot to ask my questions ;o)
What does heapCensus mean ?
What can I do to avoid this error ?
I have compiled all files with the -prof and the -auto-all flag.
When starting the program
* without any RTS options - everything is OK
* with +RTS -p-
Title: RE: fatal error; There might be a bug in the compiler
I have searched high and low for the cause of the error. There are no cases where a value depends on itself, so I suspect a compiler problem, or something in the evaluation that is more subtle. I have put the whole set of code below
Title: fatal error
I
guess I should tell what version of compiler I am using:
4.05
Mike
-Original Message-From: Michael A. Jones
[mailto:[EMAIL PROTECTED]]Sent: Monday, June 05, 2000 6:12
PMTo: [EMAIL PROTECTED]Subject: fatal
error
I made a few changes to a program and
main: fatal error: No threads to run! Deadlock?
[..]
It was mentioned to me that trace can cause this problem. However, I am not
using trace. Does anyone know any other causes?
One last thing, I am not doing any kind of multithreading on my own, but I
am using a lot of infinite lists.
Title: RE: fatal error
Keith,
I think you are right about the black hole, but I don't see how my code causes it. I have put the offending function below for you to see. If I remove the recursive calls to polyR, I do not get the deadlock.
Mike
-- Return a Lagrange polynomial
