From: hlu@eecs.wsu.edu (H.J. Lu) Subject: ANSWER: (Re: GCC report segmentation fault and dump core.) Date: 7 Oct 1992 17:01:59 GMT
In article <1992Oct7.082419.10458@nntp.hut.fi>, mjalava@lk-hp-10.hut.fi (Mika Matti Jalava) writes:
|> In article <BvpEpB.1xK@usenet.ucs.indiana.edu> tqhoang@silver.ucs.indiana.edu (Toan Hoang ~{) writes:
|>
|> >WHen ever I tried to compile a C
|> >code, it would give me a segmentation fault and dump core, even running the
|> >gcc alone will do so.
|>
|> You might suffer from the file corruption problem. The newer kernels
|> are not very reliable with some hard disks and files may get corrupted
|> when written to the disk. Try installing again. It may not work even
|> then, I had to install the biggest parts of the compiler on a floppy
|> to be able to compile the kernel with HD_DELAY set in hd.c. That
|> helped a little.
|>
[...]
I have seen quite a few people getting segmentation fault and dump core
when they run something under Linux. I may have the answer for the
problem.
If you have a fast CPU (> 25 MHz), please check your RAM. If the speed
of RAM is slower than 60ns, you may be in big trouble. Don't tell me
it runs well under DOS. Linux is a protected mode OS. My 386sx-16
without cache uses 80ns RAM. For a fast CPU, anything slower than 60ns
may not work very reliably. You have a few choices:
1. Get fast RAM. (should always work)
2. Get a big cache for CPU, like > 256k. (may work)
3. Increase wait state of your RAM. (may work)
4. Turn off turbo. (should always work)
H.J.