Ooops for previous incomplete summary message; finger got ahead
of my brain.
Many thanks to the many useful responses covering all my questions.
The problem was caused by the data size limit being too small.
I think the clue that is wasn't a system swap problem was that I was
not getting an indication of any swap activity. In fact, on the vm limit
on the failing machine was higher than on the OK machine, but the
data size limit was lower on the failing machine. As often happens, the
error message may not point directly to the cause.
Thanks again to all who responded.
Ric
Original posting:
A user has a large fortran program that gives the following error message
when compiling:
Fatal: Insufficient virtual memory to continue compilation.
This is on a GS60E, TU64 version 5.0a, 4GB RAM. Compiler is f77 V5.3-915.
swapon -s shows 3.73GB of allocated space and 98% free.
I have attempted to monitor swap via top and dxproctuner, but do not get an
indication that
swap is going to zero.
This program is compiled successfully on another machine which has 8678MB of
swap.
I would like to know how I can determine whether I truly do not have enough
swap, or
whether the compiler may not know how much swap is available? Also, how can
I "monitor"
swap while compiling to get a better picture of what is going on? Lastly,
how do I add additional
swap space. On SGI, one can add by creating a swap file and telling swap
about it. Is it that
simple on Compaq?
Received on Fri Jan 12 2001 - 19:59:07 NZDT