[Bug c++/40217] New: gcc-4.3.1 fails to produce an error message for out of memory condition

[yuri at tsoft dot com]

I accidentally ran my FreeBSD-71 system with 3GB RAM without the swap space and
compiled a large module with high degree of optimization.

I was getting this error:
{standard input}: Assembler messages:
{standard input}:68321: Warning: end of file not at end of a line; newline
inserted
{standard input}:69363: Error: undefined symbol `.LLSDACSE3986' in operation    
{standard input}:69427: Error: undefined symbol `.LFB398' in operation          
g++: Internal error: Killed: 9 (program cc1plus)                                
Please submit a full bug report.                                                
See <http://gcc.gnu.org/bugs.html> for instructions.                            

This happened 100% of time, and error message stayed the same.
So gcc was getting memory allocation failure but instead of failing with the
relevant message it was passing wrong assembly to 'as'.
Adding swap cured the situation.
gcc-4.3.3 was failing in a similar way but with a bit different error message.

This should be fixed to make gcc more reliable in the random user environments.

Today by googling the above error messages you can get a lot of references of
similar situations happening to various people.


-- 
           Summary: gcc-4.3.1 fails to produce an error message for out of
                    memory condition
           Product: gcc
           Version: 4.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: yuri at tsoft dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40217