public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zackw at panix dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/68038] New: "Internal compiler error: Killed: program cc1" should read "Virtual memory exhausted"
Date: Wed, 21 Oct 2015 02:31:00 -0000	[thread overview]
Message-ID: <bug-68038-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68038

            Bug ID: 68038
           Summary: "Internal compiler error: Killed: program cc1" should
                    read "Virtual memory exhausted"
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zackw at panix dot com
  Target Milestone: ---

99+% of the time, when the compiler proper dies on signal 9, it's because we're
on Linux and the out-of-memory killer has killed the compiler proper because it
ate all available RAM.  But the error message you get when this happens
*sounds* like there's a bug in GCC.

I suggest the driver be changed to special-case SIGKILL and print a different
message, along the lines of

   gcc: compilation process (cc1) killed by SIGKILL
   This almost always means your computer does not have enough RAM to
   compile this program.  Try adding swap space or reducing the
   number of concurrent compile jobs.


             reply	other threads:[~2015-10-21  2:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21  2:31 zackw at panix dot com [this message]
2015-10-21  2:33 ` [Bug driver/68038] " pinskia at gcc dot gnu.org
2015-10-22 14:40 ` d.u.thibault at bigfoot dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-68038-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).