No, the timer thread starts even without -threaded.
If you use -threaded it gets worse because then you have
a bunch of other threads that don't exit properly.
-- Lennart
Quoting Simon Marlow <[EMAIL PROTECTED]>:
Lennart Augustsson wrote:
I've found more bugs. There are several race conditions when a DLL
is unloaded. The extra threads that the GHC runtime system starts
(at least one is always started to generate timer ticks) are not
shut down in a synchronized way. This means that they might be
scheduled to run after the DLL has been unloaded. Which gives you
an access violation.
I don't have a proper fix for this yet.
Is this with -threaded?
Simon
_______________________________________________
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
