This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 10 Jun 2011 21:10:32 +0000
- Subject: [Bug c++/49351] Internal error: Segmentation fault (program cc1plus)
- Auto-submitted: auto-generated
- References: <bug-49351-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-06-10 21:10:16 UTC ---
does 'ulimit -a' show any limit on memory size?
obviously it would be good if gcc didn't use so much memory, but I did verify
that given a sufficiently beefy machine (64-bit, 24GB RAM) gcc 4.5.2 can
compile the .ii, so I think your segfault is due to running out of memory
rather than hitting a null pointer deference or other bug in gcc itself