Appearently the shell was not allocating enough memory to the
process. There were 2 work arounds to get the code working:
1. Run csh, and execute 'unlimit'.
2. In bash (the default shell), execute 'ulimit -s 32768' (This was
the hard limit 'ulimit -s -H')
After executing the above command the program was able to run fine.
Here's the original problem:
>I have a user who has written a simulation which deals with a fairly
>large array. When the array is 142^2 items long it runs fine, but
>as soon as he increases the number to 143 or above the program
>crashes. The program runs fine on SGI, Linux, and Solaris.
>
>While fiddling with this problem, I was able to write a program to
>travers an array 256^2 (65536) elements long without any problem.
>
>By expermentation I've figured out that the error is cause by some
>code after a certain line number, unfortunetely when I try to use
>ladebug to figure out the offending command it will not even run the
>first line 'cout << "Test" << flush;', it gives an error "thread
>received signal SEGV".
>
>Does anyone have ideas what might be the problem?
>
thanks,
James
--
----------------------------------------------------------------------------
James Hammett
ACITS (Academic Computing) CPE 4.468
Chemical Engineering Unix Support 471-9701
----------------------------------------------------------------------------
An injustice anywhere is a threat to justice everywhere - MLK jr.
----------------------------------------------------------------------------
Received on Wed Jan 31 2001 - 14:58:41 NZDT