Re: c++/5818: cc1plus crashes if it runs out of memory

Re: c++/5818: cc1plus crashes if it runs out of memory

[ebotcazou]

Synopsis: cc1plus crashes if it runs out of memory

State-Changed-From-To: analyzed->closed
State-Changed-By: ebotcazou
State-Changed-When: Mon Mar  3 21:01:33 2003
State-Changed-Why:
    On submitter's request: http://gcc.gnu.org/ml/gcc-bugs/2003-03/msg00129.html

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5818

Re: c++/5818: cc1plus crashes if it runs out of memory

[nathan]

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

c++/5818: cc1plus crashes if it runs out of memory

[lloyd]

>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: