Virtual memory exhausted...

Virtual memory exhausted...

[John.Velman]

When compiling XSB version 2.2 with the default CFLAGS  (which
included a -O4)  I got a "virtual memory exhausted" message.

Initially, this machine had been set up with 150M of virtual memory
(and 64K of physical memory).   According to task manager, it
bombed at about 200K of total memory commit, which seemed
about right.   I  spent a lot of time getting rid of unnecessary
stuff on my hardrive, and increased the virtual memory
allocation to 500MB.

Same result.  gcc threw in the towel when total memory
use was about 200MB, even though task manager showed
that there was over 300MB remaining.

There were some rather old messages related to "virtual
memory exhausted" in the mail archives, but I was unable
to find anything helpful.

?

(By the way, I got it to build by removing optimization
entirely. )

Running cygwin 1.4.1 on NT4 SP 5.

John Velman
john.velman@hsc.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Virtual memory exhausted...

[Randall R Schulz]

John,

According to David Warren, one of the principals of the XSB project (it has 
its own mailing lists, you know), this is a known problem. He told me he 
just compiles the one source file that gives the error with a lower 
optimization level.

I accomplish this by adding one rule to the configure-produced makefile 
that specifies a lower optimization level for the problematic file (I'd 
tell you exactly which level I used and the name of the source file, but I 
don't have access to the machine with that information at the moment. It 
was not higher than -O2, I'm pretty sure, and I think the file was 
something like "emuloop.c").

For me this symptom appears under Windows 2K Pro with the first service 
pack installed.

However, if someone here can answer the question as to why this limit is 
hit (I got it on a system with  512 megabytes of physical memory), I'd be 
interested to hear it. I've  assumed it is an idiosyncrasy either of gcc or 
the Cygwin memory management and not a bug, per se.

And I'd sure like to know where you got that copy of cygwin 1.4.1, though...

Randall Schulz
Teknowledge Corp.
Palo Alto, CA USA


At 12:37 PM 09/25/2000 , John.Velman@HSC.com wrote:
>When compiling XSB version 2.2 with the default CFLAGS  (which
>included a -O4)  I got a "virtual memory exhausted" message.
>
>Initially, this machine had been set up with 150M of virtual memory
>(and 64K of physical memory).   According to task manager, it
>bombed at about 200K of total memory commit, which seemed
>about right.   I  spent a lot of time getting rid of unnecessary
>stuff on my hardrive, and increased the virtual memory
>allocation to 500MB.
>
>Same result.  gcc threw in the towel when total memory
>use was about 200MB, even though task manager showed
>that there was over 300MB remaining.
>
>There were some rather old messages related to "virtual
>memory exhausted" in the mail archives, but I was unable
>to find anything helpful.
>
>?
>
>(By the way, I got it to build by removing optimization
>entirely. )
>
>Running cygwin 1.4.1 on NT4 SP 5.
>
>John Velman
>john.velman@hsc.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Virtual memory exhausted...

[Earnie Boyd]

--- John.Velman@HSC.com wrote:
> When compiling XSB version 2.2 with the default CFLAGS  (which
> included a -O4)  I got a "virtual memory exhausted" message.
> 

Could be a peculiar to -O4.  What happens if you `make CFLAG=-O2'?  NOTE: You
may need to add other flags.

Cheers,

=====
--- < http://earniesystems.safeshopper.com > ---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Virtual Memory Exhausted

[Earnie Boyd]

---Gord Wait <Gord_Wait@spectrumsignal.com> wrote:
>
> Using Cygwin32 Beta 19 I tried compiling a linux ap (vbs a free
verilog
> simulator) under the bash shell
> and got the Virtual Memory Exhausted error after a few .o files were
built. 
> Help?

How much free disk space do you have on the boot disk?  Win95 VM is
relative to the amount of free disk space.

> Also, I tried compiling Perl 5 and get random "permission denied" on
bourne
> shell scripts.
> Sometimes the scripts will execute, sometimes they won't. 

Don't know.  Could be a race problem with the file getting completely
close and a request to rename or delete it.

> Win-95 OSR2 on an HP 166 pentium with 64 meg ram is the box in
question..

Check out the Win95!! section on my pages.

==
-                \\||//
-----------o0O0--Earnie--0O0o------------
--        earnie_boyd@yahoo.com        --
-- http://freeyellow.com/members5/gw32 --
--------------ooo0O--O0ooo---------------

PS: Newbie's, you should visit my page.
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Virtual Memory Exhausted

[Gord Wait]

Using Cygwin32 Beta 19 I tried compiling a linux ap (vbs a free verilog
simulator) under the bash shell
and got the Virtual Memory Exhausted error after a few .o files were built. 
Help?
Also, I tried compiling Perl 5 and get random "permission denied" on bourne
shell scripts.
Sometimes the scripts will execute, sometimes they won't. 
Win-95 OSR2 on an HP 166 pentium with 64 meg ram is the box in question..
Thanks
Gord Wait

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".