Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Subject:	Virtual memory exhausted...
To:	cygwin AT sources DOT redhat DOT com
From:	John DOT Velman AT HSC DOT com
Date:	Mon, 25 Sep 2000 12:37:48 -0700
Message-ID:	<OF51DA9F86.FCC004E2-ON88256965.006B1ADF@hughes.com>
X-MIMETrack:	Serialize by Router on MTA00/HUGHES(Release 5.0.2c |February 2, 2000) at 09/25/2000
	12:37:52 PM
MIME-Version:	1.0

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 DOT velman AT hsc DOT com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -