3 Importance: Normal a follow-up to close (hopefully) this thread. i couldn't repeat the error on other platforms (windows + rh9) and started to become suspicious that my system was unstable (it's been rock solid for years). first suspect was the kernel, but compiling a kernel triggered another error and then a bios warning - turns out that a fan has failed on the motherboard. so i guess that the memory problems are related to overheating (memcheck86 didn't detect any problems). no bug to report here. thanks for the help from various people via email. if anyone happens to know of a source of replacement chipset fans for AOpen mobos in S America I'd be grateful for a contact... ;-/ cheers, andrew andrew cooke said:
no, i'm not sure it's segfaulting (i should have used a less
specific > term), but i am seeing memory related errors. i've had messages in the > syslog that describes a null pointer passed to the kernel and i've also > just seen an error on stderr that says
internal error: evacuate: strange closure type 39216 Please report this as a bug to
the trouble is that when if first got the error with ghc5, i updated my > system. not only ghc, but also a slew of other
glasgow-haskell-bugs@haskell.org, > or http://www.sourceforge.net/projects/ghc/ > packages. now i'm worried > that there are two different errors (one possibly related to X or > Mozilla), or even that ghc is merely the victim of an error in some other > program.
i'm about to run the program on windows, using the parameters that
once i'm a little clearer on what's happening i'll file a bug report. i > just wondered whether there was any way of getting the system to give more > informative errors when it dies (eg recompiling ghc in some kind of debug > mode).
cheers, andrew
ps. just got a segmentation fault re-running the code that
gave > that message, to see if i can reproduce it. so far my attempts to > restrict the program scope and repeat the error have failed. > previously > gave the error above :o/
Volker Stolz said:
In local.glasgow-haskell-users, you wrote:
I have a ghc program that appears to be causing a memory error
(either >>> segfaulting or tripping up X and killing my session).
Are you sure it's segfaulting? You might simply run low on memory
and >> your system starts killing processes to free up memory.
Maybe you can find more details in the syslog. -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME rage against the finite state machine
-- http://www.acooke.org/andrew _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users