(Hello Ian, nice to hear from you again . . .)
Simon Marlow wrote:
[snip]
But before I dive in on this one, could you possibly test it again with a
more recent GHC - I've made a few changes to our flaky concurrent I/O system
since 19990916.
[snip]
I'm afraid the FCIS is still F, or at least
Simon Marlow writes ("RE: Deadlock again (was Re: GHC 4.04.19990916 produces
coredumpin g executable)"):
No doubt you're quite tired of seeing my mails by now, but here, have
another one :-).
I now have a couple of problems which look like they can be summarised
as `race
On Sun, Jan 02, 2000 at 18:36:41 +, Ian Jackson wrote:
-davenant:stalk ./nettlestalk
ready
seqd
nettlestalk: fatal error: No threads to run! Deadlock?
-davenant:stalk
The problem is in NettleAction.hs:
\begin{code}
runGame_noUnitNotifs :: Game - Timestamp - [Callback] - GM rt -
Before Christmas I reported a (known, I discovered) bug which would
result in the message `fatal error: No threads to run! Deadlock?'.
Simon Marlow replied then:
This is due to a locking problem with our I/O library. Basically, if the
program calls trace while writing to stdout (eg. using
I wrote:
I have a program (no doubt pretty grotty - I'm still messing around
learning Haskell) which causes GHC (4.04.19990916) to produce an
executable which coredumps.
...
I'm using a GHC binary package from Debian GNU/Linux, binary package
version 4.04.19990916-0slink1 built by Michael
Ian Jackson [EMAIL PROTECTED] wrote,
I wrote:
I have a program (no doubt pretty grotty - I'm still messing around
learning Haskell) which causes GHC (4.04.19990916) to produce an
executable which coredumps.
...
I'm using a GHC binary package from Debian GNU/Linux, binary package
[...]
-davenant:stalk ./nettlestalk
foo
Segmentation fault (core dumped)
I'm using 4.04.19990916-2 and it doesn't coredump, but shows the same
deadlock error, you mentioned in the other mail:
[509]$ ./nettlestalk
foo
nettlestalk: fatal error: No threads to run! Deadlock?
This
