public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amit.chitnis at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58144] New: Receive "virtual memory exhausted: Cannot allocate memory" while compiling
Date: Tue, 13 Aug 2013 01:30:00 -0000	[thread overview]
Message-ID: <bug-58144-4@http.gcc.gnu.org/bugzilla/> (raw)

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/


             reply	other threads:[~2013-08-13  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13  1:30 amit.chitnis at gmail dot com [this message]
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

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=bug-58144-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).