Bug 1273484
Summary: | CentOS7 problem with gcc | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Daniel U. Thibault <d.u.thibault> |
Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | qe-baseos-tools-bugs |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 | CC: | mfranc, mpolacek |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-21 08:18:01 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Daniel U. Thibault
2015-10-20 14:25:59 UTC
This almost always means that the machine doesn't have enough memory and the OOM killer kills the cc1 process. Indeed, increasing the virtual machine's memory solved the problem. So I guess teh bug should be relabelled something like 'gcc should report out-of-memory errors in a more obvious way'. Because that error message was pretty well obfuscated. There's an upstream PR for this now: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68038 I think we can close this bug now; please reopen if you have any further questions. |