[EMAIL PROTECTED] (S.D.Mechveliani) writes:
> For the below program, ghc-4 -c -fglasgow-exts Main.hs
> ghc-4 -o run Main.o
> ./run
> yields
> `run: fatal error: No threads to run! Deadlock?'
>
> instead of infinite recursion for the value of `s' - the latter has to
> overflow the stack.
As I said in my previous message, the above error may indicate an
infinite loop. What actually happened is that the thread blocked
against itself, which the system interpreted as deadlock.
> Commenting out (the dummy) operation cv in the class C, returns to the
> correct behaviour.
>
> Another point.
> Some slight changes of this program caused a strange warning,
> something near
> ghc123.* ..closure as static but referred ..in.. as dynamic..
If this is a warning, it can safely be ignored.
Cheers,
Simon
--
Simon Marlow [EMAIL PROTECTED]
University of Glasgow http://www.dcs.gla.ac.uk/~simonm/
finger for PGP public key
