public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: lloyd@acm.jhu.edu To: gcc-gnats@gcc.gnu.org Subject: c++/5818: cc1plus crashes if it runs out of memory Date: Sun, 03 Mar 2002 09:16:00 -0000 [thread overview] Message-ID: <20020303170635.24529.qmail@sources.redhat.com> (raw) >Number: 5818 >Category: c++ >Synopsis: cc1plus crashes if it runs out of memory >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Mar 03 09:16:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: lloyd@acm.jhu.edu >Release: gcc 3.0.4 >Organization: >Environment: Redhat Linux 7.2 AMD Athlon >Description: Very minor. I was having problems with a bug causing the allocation of hundreds of megabytes of memory, swapping my machine to death, so I set my memory ulimts to something like 16 megabytes. Then I compiled some code. A few times, GCC died with warnings that virtual memory was exausted. But once, I got this: g++: Internal error: Segmentation fault (program cc1plus) Please submit a full bug report. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. So it seems that in at least one case, GCC isn't checking it's system call returns properly (GCC compiles my code without problems when the memory ulimits are set higher, so I'm quite certain this is not a code-dependant thing) >How-To-Repeat: Set your ulimits for memory very low. Compile something. >Fix: Make sure malloc doesn't return zero? :) >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-03-03 17:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-03 9:16 lloyd [this message] 2002-09-15 11:55 nathan 2003-03-03 21:01 ebotcazou
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=20020303170635.24529.qmail@sources.redhat.com \ --to=lloyd@acm.jhu.edu \ --cc=gcc-gnats@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: linkBe 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).