On Tue, Aug 03, 1999 at 01:49:36 -0700, Simon Marlow wrote:
Yesterday's sources were fully broken due to a bogus commit made by me.
Things should be ok now.
Bad luck to me :-(
However, I just wanted to give some feedback that now it's working again
(1999/08/03) on Linux (packages downloadable
Hmmm, just a me-too :-(
it dies very quickly, just after a couple of calls to times according
to strace and possibly in a function called Main_main_info() according
to gdb.
k
Michael Weber writes:
But my core dumps, don't give any "blahblah exception (core dumped)"
messages.
I wish, I could have provided more debugging info, but
strace's and gdb's
output isn't very helpful at all. How do I enable those
IF_DEBUG(...) macros
(or something that helps tracking down the problem)? I tried,
but it seems I
overlooked something...
I add the following lines to my
$ cat tmp.lhs
module Main( main ) where
main = putStr $ show q
where q = quot 1 0
$ ghc-4.02 tmp.lhs
ghc-4.02: module version changed to 176; reason: usages changed
1006 swift ~/ghc/constraints/mixed
$ a.out
Fail: Prelude.Integral.quot{Integer}: divide by 0
1007 swift
: Hi!
:
: I tried to recompile the latest ghc (1999/07/31) on a Linux/glibc2.1.1
: system (egcs 2.91.66), but there seems to be a problem: the build works, but
: the resulting compiler produces executables, that throw core, even with
: "main = return ()".
I've noticed that as well. Code like
Hi!
I tried to recompile the latest ghc (1999/07/31) on a Linux/glibc2.1.1
system (egcs 2.91.66), but there seems to be a problem: the build works, but
the resulting compiler produces executables, that throw core, even with
"main = return ()".
I have a CVS version from 1999/07/10, and this one
On Mon, Aug 02, 1999 at 12:54:23 +0100, Marc van Dongen wrote:
[...]
I've noticed that as well. Code like
does not produce proper error messages anymore which it did with
ghc-4.02. One wonders where the performance boost came from:-)
$ cat tmp.lhs
module Main( main ) where
main =
