Lucid Dream wrote:
>
> I have a Pentium 200, and everything is cool to the touch.
>
> I tend to be compiling a LOT, and my computer runs 24/7. This is the only
> program which throws this error at me.
Don't get confused by this. Compilation is a very thorough test of
hardware under Linux. The gcc uses a _lot_ of pointers, a _lot_ of
resources and strains the hardware to the limit. Other programs will not
give you a Signal 11 so easily simply because they don't strain the
hardware enough.
Don't be confused by the fact that under M$ Windblows everything is OK.
They access the memory using a much slower approach (using segments,
offsets etc, instead of directly and linearly, as Linux does). Linux
accesses the hardware closer to the specs, so if your hardware is broken
(in this case your memory chips), you will probably get to know it only
under Linux and gcc.
Again, change your memory chips!
Chris
