Summary: | www-client/chromium-12.0.742.53 gcc-4.4.5 internal compiler error: Segmentation fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Norman Shulman <norman.shulman> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Norman Shulman
2011-05-13 16:32:29 UTC
I think a segfault from gcc generally points to bad memory (RAM). Can you run memtest for a few hours to see if you get any errors? (In reply to comment #1) I'll run it overnight. Reran the emerge command and it completed successfully, so this may well be a memory problem. Okay. Reopen if you get a consistent failure. Left memtest86+ running Friday night; workstation rebooted on Saturday. Started memtest86+ last night; still running when I came in this morning, no errors. Ok. Can you reproduce the compiler error? No; I re-emerged chromium overnight without error. (In reply to comment #7) > No; I re-emerged chromium overnight without error. By the way, I think it was ccache. How can ccache cause an internal compiler error? Presumably everything in ccache has already been through the compiler without error. Thanks. (In reply to comment #9) > How can ccache cause an internal compiler error? Presumably everything in > ccache has already been through the compiler without error. ccache is of course only a guess, but I've seen cases where cache corruption was leading to strange errors later (usually on linking). |