public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/58144] New: Receive "virtual memory exhausted: Cannot allocate memory" while compiling
@ 2013-08-13 1:30 amit.chitnis at gmail dot com
2013-08-13 8:36 ` [Bug c++/58144] " redi at gcc dot gnu.org
2015-03-25 19:12 ` paolo.carlini at oracle dot com
0 siblings, 2 replies; 3+ messages in thread
From: amit.chitnis at gmail dot com @ 2013-08-13 1:30 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58144
Bug ID: 58144
Summary: Receive "virtual memory exhausted: Cannot allocate
memory" while compiling
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: amit.chitnis at gmail dot com
g++ (GCC) 4.4.6 20130305 (Red Hat 4.4.6-4).
Steps to reproduce
1. create a small hello world program with iostream,stdio.h and stdlib.h
using namespace std;
2. create a big file (say 900M) named "new" in a location which is a part of
your include path.
3. Compile the hello world cpp and it should fail with the above error. This
seems to be because of the size and name of the file created in step 2 above.
g++ -g -pthread -D_THREAD_SAFE -D_REENTRANT -I/opt/performance -o helloworld.o
-c helloworld.cpp
file "new" was created at location /opt/performance/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/58144] Receive "virtual memory exhausted: Cannot allocate memory" while compiling
2013-08-13 1:30 [Bug c++/58144] New: Receive "virtual memory exhausted: Cannot allocate memory" while compiling amit.chitnis at gmail dot com
@ 2013-08-13 8:36 ` redi at gcc dot gnu.org
2015-03-25 19:12 ` paolo.carlini at oracle dot com
1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2013-08-13 8:36 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58144
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Amit Chitnis from comment #0)
> 2. create a big file (say 900M) named "new" in a location which is a part of
> your include path.
This is your problem, <new> is a standard header so you must not replace it.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/58144] Receive "virtual memory exhausted: Cannot allocate memory" while compiling
2013-08-13 1:30 [Bug c++/58144] New: Receive "virtual memory exhausted: Cannot allocate memory" while compiling amit.chitnis at gmail dot com
2013-08-13 8:36 ` [Bug c++/58144] " redi at gcc dot gnu.org
@ 2015-03-25 19:12 ` paolo.carlini at oracle dot com
1 sibling, 0 replies; 3+ messages in thread
From: paolo.carlini at oracle dot com @ 2015-03-25 19:12 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58144
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC|amit.chitnis at gmail dot com |
Resolution|--- |FIXED
--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Closing then.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-03-25 19:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-13 1:30 [Bug c++/58144] New: Receive "virtual memory exhausted: Cannot allocate memory" while compiling amit.chitnis at gmail dot com
2013-08-13 8:36 ` [Bug c++/58144] " redi at gcc dot gnu.org
2015-03-25 19:12 ` paolo.carlini at oracle dot com
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).