<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Malcolm Wallace wrote:
<blockquote
cite="mid20050217121510.613848e7.Malcolm.Wallace@cs.york.ac.uk"
type="cite">
<pre wrap="">Seth Kurtzberg <a class="moz-txt-link-rfc2396E" href="mailto:seth@cql.com"><seth@cql.com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">There has to be one, because the problem occurs when you compile gcc
with gcc. I'll look for a specific bug report. It happens much more
frequently with 3.x than with 2.95, in my testing, but that was not a
test of compiling Haskell, so I have no frequency information, specifically.
</pre>
</blockquote>
<pre wrap=""><!---->
Sounds like a CPU-overheating problem to me. It is well known that
running an inadequately cooled processor at 100% for an extended
period will cause random crashes. There are third-party reports
that it happens with Linux kernel builds, and I have personally seen
it with builds of nhc98 and Hat. When I replaced the CPU fan, the
problems disappeared.
</pre>
<blockquote type="cite">
<pre wrap="">The other problem for the gcc people is the fact that it occurs
randomly. The behavior has changed; 3.4 will crash in a different place
than 3.3. If the program is large enough, it will happen.
</pre>
</blockquote>
<pre wrap=""><!---->
Non-repeatable crashes certainly point the finger first at hardware
rather than software. Could also be deteriorating memory chips -
but that is likely to bring the whole machine down eventually.
Regards,
Malcolm
</pre>
</blockquote>
Ordinally I would agree, but in this cases it hash to be software
because I got probem on 40 different solais system<br>
<br>
As for the processor overheating, you would expect that it's on it's
last legs if it starts overheating. It also happens on older machies;
I've seen it happen on a PII machine, which isn't terribly hot.<br>
<br>
I think that because I've seen it so many times, on machines that
continue to run flawlessly, some for two years, we can eliminate
hardware. This is almost certainly heap corruption. The KDE tool that
is like purify (only better and free), valgrind, should help fix it if
it is caused by any sort of memory corruption. That would be <br>
<br>
Remember, it is always crashing (I believe always) with an internal
compiler error. Were hardware involved, you would expect to not get
the same message. (Unless its the only error they have a name for).<br>
<br>
If you really want to fix it, we could use a watchdog timer, and have
it restart the compiler whenever it crashes.<br>
<blockquote
cite="mid20050217121510.613848e7.Malcolm.Wallace@cs.york.ac.uk"
type="cite">
<pre wrap="">_______________________________________________
Glasgow-haskell-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Glasgow-haskell-users@haskell.org">Glasgow-haskell-users@haskell.org</a>
<a class="moz-txt-link-freetext" href="http://www.haskell.org/mailman/listinfo/glasgow-haskell-users">http://www.haskell.org/mailman/listinfo/glasgow-haskell-users</a>
!DSPAM:42148f7e119355211311528!
</pre>
</blockquote>
<br>
</body>
</html>