Simon Peyton Jones ([EMAIL PROTECTED]) wrote:
: | This is really a big problem. I have been strugling with it
: | myself. The safest thing to do is to use `error' (sad but
: | true). That's the only thing I can recommend:-(
:
: This is a long-standing and embarassing bug which is
: alas not quic
| This is really a big problem. I have been strugling with it
| myself. The safest thing to do is to use `error' (sad but
| true). That's the only thing I can recommend:-(
This is a long-standing and embarassing bug which is
alas not quick to fix. But have now been embarassed fo
often that we (a
Sorry about this. I forgot to group reply.
- Forwarded message from Marc van Dongen <[EMAIL PROTECTED]> -
Date: Fri, 7 Apr 2000 09:55:12 +0100
From: Marc van Dongen <[EMAIL PROTECTED]>
To: "Michael A. Jones" <[EMAIL PROTECTED]>
Subject: Re: Debugging techniq
Title: RE: Debugging techniques
In
Main.main, change it from
main = whatever
to
main = stderr `seq` whatever
(you
may have to import IO to bring stderr into scope.)
--sigbjorn
-Original Message-From: Michael A. Jones
[mailto:[EMAIL PROTECTED]]Sent: Thursday, April
Title: RE: Debugging techniques
Well, I tried the trace function as was recommended, linking in IOExts and all, but I get the following error when I run the application:
main: fatal error: No threads to run!: Deadlock?
The statement where it is used is:
datalogQueryHistogramResult
execution
> never reached the let.
Well, laziness is exactly about this, and unfotunately it makes
conventional debugging techniques inappropriate.
Haskell's laziness includes the rule that mere evaluation of
an expression cannot cause any visible side effects other than
nontermination.
Title: Debugging techniques
Hi,
I have a question on debugging, but first I must say that I am a bit of a newbie. I have ML experience, but Haskell is a bit new to me. Second, perhaps you can suggest a place I can ask newbie questions that is more appropriate than this list.
Are there any
