public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: nathan@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, lloyd@acm.jhu.edu, nobody@gcc.gnu.org Subject: Re: c++/5818: cc1plus crashes if it runs out of memory Date: Sun, 15 Sep 2002 11:55:00 -0000 [thread overview] Message-ID: <20020915185501.22830.qmail@sources.redhat.com> (raw) Synopsis: cc1plus crashes if it runs out of memory State-Changed-From-To: open->analyzed State-Changed-By: nathan State-Changed-When: Sun Sep 15 11:55:01 2002 State-Changed-Why: of course we chyeck malloc's return. Unfortunately some systems overcommit memory. I.e. they say 'here's a pile of memory', but then only attempt to allocate the pages when you try and use them. At that point, you get a seg fault. Maybe there's a way of saying 'don't give me overcommitted pages'. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5818
next reply other threads:[~2002-09-15 18:55 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-15 11:55 nathan [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-03 21:01 ebotcazou 2002-03-03 9:16 lloyd
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=20020915185501.22830.qmail@sources.redhat.com \ --to=nathan@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=lloyd@acm.jhu.edu \ --cc=nobody@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).