What does the message “Internal compiler error: cc1 got fatal signal 11,4” mean ?
Ans: Gcc is probably the biggest memory hog you’re likely to run on your machine and it will surely eat up a lot of your RAM. Usually a fatal signal 11 will mean some sort of parity errors in your RAM or other hardware faults. I had this once when `cc1′ got corrupted due to a race condition and bad blocks on my hard disk. There have also been reports that overheating chips, (not french fries), can also produce such errors. And watch for poor IDE controller/drive combos that are being run faster than the standard 8MHz AT bus clock. These can give the same errors by causing corruption of the swap space. Usually, a signal 11 (segmentation violation) means that a process tried to access memory out of its process space, or tried to write into a read-only location. Sometimes, this signal is caused by software bugs, not by hardware faults (or your system would hang repeatedly, because the same thing happened to the kernel). With gcc 2.3.3, some people could reproduce a lot of “signal 11″‘s. A
Related Questions
- Why does my kernel compilation stops at random locations with: "Internal compiler error: program cc1 caught fatal signal 11."?
- I got the error message, "Error in loading XML Parser", when launching Chatopus. What does that mean?
- What does the message "Internal compiler error: cc1 got fatal signal 11,4" mean ?
