Summary: | gcc segfaults while compiling large packages | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kacper Kopczynski <capsel> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Lowest | ||
Version: | 2008.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kacper Kopczynski
2008-07-06 12:01:46 UTC
You haven't argued why the gcc version is important so I removed that from the Summary. It does look as though the processor overheats while compiling large packages (as it manages to compile smaller ones without trouble), perhaps corrupting some L1 or L2 cache's content in the process (as Linux apparently keeps running, only a small amount of memory is concerned so it's unlikely your RAM is overheating). You should probably investigate your system's hardware (or a software solution that controls the system's climate) before you lay the blame on the software. Please reopen this bug if and when you can pinpoint the exact code that triggers this bug and when you can pinpoint it to an exact GCC version by way of elimination. If it is hardware why everything else works? Why nothing else segfaults? Temperature is not controlled by OS, only settings are in BIOS, and as I wrote - they are SAFE. Max RPMs for fans, lowest speeds of everything I've found, but I haven't touched power settings - they are "auto" controlled. As about "the exact code" - I thought those files are exact code, aren't they? If it is overheating problem why it shows up at same files every time? |