Date:	Tue, 29 Apr 97 16:17:50 UT
From:	"Ron Stawicki" <r_stawicki AT msn DOT com>
Message-Id:	<UPMAIL16.199704291618450131@msn.com>
To:	fighteer AT cs DOT com
Cc:	djgpp AT delorie DOT com
Subject:	RE: virtual memory exhausted

----------
From: 	John M. Aldrich
Sent: 	Sunday, April 27, 1997 1:18 PM
To: 	Ron Stawicki
Subject: 	Re: virtual memory exhausted

Ron Stawicki wrote:
> 
> Compiling an HP C++ toolkit, and getting a virtual memory exhausted
> error emitted.
> 
> The HP toolkit is large in size, but not huge (<<<1 Meg).

According to the FAQ (v2/faq210b.zip) chapter 6.3, this error is usually
caused by a complex C++ structure that causes cc1plus.exe to run out of
stack space when compiling.  Use the 'stubedit' program to increase the
minimum stack of cc1plus.exe to 1024k or something similar, and try
again.  And definitely read that section of the FAQ.

!!!!!!!!!!!!!!!!

I thank you and Eli Zaretskii for your response; also downloaded the faq 
as you recommended, and reviewed it.

Used stubedit cc1plus.exe to increase the stack size. The HP code
is a set of include files which represents a very large object. When I 
increase the stack space, the compiler actually gets through fewer
include files before emitting the virtual memory exhausted error.

I also have a few questions:

1) WIN95 provides a virtual memory manager; is this just specific to
windows, or does it tie in?

2) WIN95 has native DPMI, or is that what is provided by EMM386?

3) Does CSDPMI conflict with the native DPMI?

4) As mentioned above, what would cause cc1plus to emit virtual 
exhausted sooner than if the stack size is set to a lower size?

Thank you for your time

 

- Raw text -