| 1 |
Raphael Melo de Oliveira Bastos Sales wrote: |
| 2 |
|
| 3 |
>Hi there, |
| 4 |
> |
| 5 |
> I'm using gcc-3.3.5.20050130-r1 and I keep getting segmentation |
| 6 |
>fault every now and then. Since it doesn't work, I can't compile an |
| 7 |
>earlier, more stable version. I hope it isn't a hardware failure, |
| 8 |
>because the warranty on my new computer just ended. It is probably not |
| 9 |
>an memory error, because I'm not using -pipe. I checked the filesystem |
| 10 |
>and no corruption was found. |
| 11 |
> |
| 12 |
> |
| 13 |
|
| 14 |
Don't be so sure. -pipe doesn't add that much additional memory |
| 15 |
overhead, in fact, only a few pages used as an IO buffer between the |
| 16 |
processes. The process of compiling itself is very tough on memory, |
| 17 |
reading and writing to various locations in rapid succession. |
| 18 |
|
| 19 |
I would say memory is the most likely problem, but it could be |
| 20 |
overheating or power supply problems also. |
| 21 |
|
| 22 |
> Anybody had this type of error too? If so, how did you handle it? |
| 23 |
>Are there any tools to check the hard drive's surface for flaws? |
| 24 |
> |
| 25 |
> |
| 26 |
|
| 27 |
Bad disk blocks are almost certainly not the issue, as you would end up |
| 28 |
with IO errors during the compilation, not segfaults. Well, I guess if |
| 29 |
your swap had bad blocks, you might get a segfault... |
| 30 |
|
| 31 |
Anyway, "dd if=/dev/hda of=/dev/null bs=4k" will test readability of |
| 32 |
your entire disk. It doesn't test the validity of your data though... |
| 33 |
|
| 34 |
-Richard |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives