public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: dbattams@canada.com
To: help-gcc@gnu.org
Subject: Help - Compilation Error: "Virtual Memory Exhausted"
Date: Sat, 11 Dec 1999 23:01:00 -0000	[thread overview]
Message-ID: <82vgn0$st5$1@nnrp1.deja.com> (raw)

I just wrote some code in (ANSI) C++, compiled it and tested it on my
Win95 box using DJGPP version 2.95.1.  Now I'm trying to port it over
to UNIX using GCC version 2.8.1, but when I try to compile it I get an
error that I've never seen before, and I've seen quite a few of them in
my experiences :-).  I've pasted the error that GCC returns below.  I'd
paste some of my code, but (1) I don't think it's the problem and (2)
if it is the problem I'm not sure which code it would be.  My code uses
some STL classes (<map>, <vector>) and also heavily relies on
<string>.  Anyway, here's the error message:

<dbattams> [~/code] $ make
g++ -Iinclude -o formParser/clsFormParser.o -c
formParser/clsFormParser.cc
/usr/include/g++/stl_function.h: In function `class
const_mem_fun1_t<S,T,A> mem_fun1(S (T::*)(A) const)':
In file included from /usr/include/g++/stl_tree.h:59,
                 from /usr/include/g++/map:31,
                 from include/clsFormParser.h:4,
                 from formParser/clsFormParser.cc:1:
/usr/include/g++/stl_function.h:608: virtual memory exhausted
*** Error code 1
Stop in /home/d/b/dbattams/c-code.

Any help with this error message, what it means, and what I might do to
fix it would be greatly appreciated.

    -- Derek Battams


Sent via Deja.com http://www.deja.com/
Before you buy.

WARNING: multiple messages have this Message-ID
From: dbattams@canada.com
To: help-gcc@gnu.org
Subject: Help - Compilation Error: "Virtual Memory Exhausted"
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <82vgn0$st5$1@nnrp1.deja.com> (raw)
Message-ID: <19991231222400.RGAa4uzQIX0qHuJvF6FxPYMVGX-9Ttfz9lVc5J2tCtE@z> (raw)

I just wrote some code in (ANSI) C++, compiled it and tested it on my
Win95 box using DJGPP version 2.95.1.  Now I'm trying to port it over
to UNIX using GCC version 2.8.1, but when I try to compile it I get an
error that I've never seen before, and I've seen quite a few of them in
my experiences :-).  I've pasted the error that GCC returns below.  I'd
paste some of my code, but (1) I don't think it's the problem and (2)
if it is the problem I'm not sure which code it would be.  My code uses
some STL classes (<map>, <vector>) and also heavily relies on
<string>.  Anyway, here's the error message:

<dbattams> [~/code] $ make
g++ -Iinclude -o formParser/clsFormParser.o -c
formParser/clsFormParser.cc
/usr/include/g++/stl_function.h: In function `class
const_mem_fun1_t<S,T,A> mem_fun1(S (T::*)(A) const)':
In file included from /usr/include/g++/stl_tree.h:59,
                 from /usr/include/g++/map:31,
                 from include/clsFormParser.h:4,
                 from formParser/clsFormParser.cc:1:
/usr/include/g++/stl_function.h:608: virtual memory exhausted
*** Error code 1
Stop in /home/d/b/dbattams/c-code.

Any help with this error message, what it means, and what I might do to
fix it would be greatly appreciated.

    -- Derek Battams


Sent via Deja.com http://www.deja.com/
Before you buy.

             reply	other threads:[~1999-12-11 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-11 23:01 dbattams [this message]
1999-12-14  3:14 ` Gaël Trinquart
1999-12-31 22:24   ` Gaël Trinquart
1999-12-31 22:24 ` dbattams

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='82vgn0$st5$1@nnrp1.deja.com' \
    --to=dbattams@canada.com \
    --cc=help-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).