This article is from the Frequently Asked Questions for Linux, the Free/Open Source UNIX-like operating system kernel that runs on many modern computer systems. Maintained by David C. Merrill with numerous contributions by others. (v1.0).
A: Your compiler (GCC) dumped core. You probably have a corrupted, buggy, or old version of GCC - get the latest release or EGCS. Alternatively, you may be running out of swap space. Refer to Why Does the Machine Run Very Slowly with GCC / X / ...?.
If this doesn't fix the problem, you are probably having problems with memory or disk corruption. Check that the clock rate, wait states, and refresh timing for your SIMMS and cache are correct (hardware manuals are sometimes wrong, too). If so, you may have some marginal SIMMS, or a faulty motherboard or hard disk or controller.
Linux is a very good memory tester - much better than MS-DOS based memory test programs.
Reportedly, some clone x87 math coprocessors can cause problems. Try compiling a kernel with math emulation (see How To Upgrade/Recompile a Kernel ). The no387 kernel command line flag on the LILO prompt to force the kernel to use math emulation, or it may be able to work and still use the '387, with the math emulation compiled in but mainly unused.
More information about this problem is available on the Web at http:// www.bitwizard.nl/sig11/.