Dominique Dhumieres wrote:
can you please try the following on your machines?
The result is:
[ibook-dhum] f90/bug% a.out no exception thrown
So that is the problem. Do you know what may be an appropriate forum where to ask why this program does not work as expected on Mac OS X?
Now looking at the man page for setrlimit, I see:
... RLIMIT_CORE The largest size (in bytes) core file that may be created.
RLIMIT_CPU The maximum amount of cpu time (in seconds) to be used by each process. RLIMIT_DATA The maximum size (in bytes) of the data segment for a process; this defines how far a program may extend its break with the sbrk(2) system call. RLIMIT_FSIZE The largest size (in bytes) file that may be created. RLIMIT_MEMLOCK The maximum size (in bytes) which a process may lock into memory using the mlock(2) function. RLIMIT_NOFILE The maximum number of open files for this process. RLIMIT_NPROC The maximum number of simultaneous processes for this user id. RLIMIT_RSS The maximum size (in bytes) to which a process's resident set size may grow. This imposes a limit on the amount of physical memory to be given to a process; if memory is tight, the system will prefer to take memory from pro- cesses that are exceeding their declared resident set size. RLIMIT_STACK The maximum size (in bytes) of the stack segment for a process; this defines how far a program's stack segment may be extended. Stack extension is performed automatically by the system.... 4th Berkeley Distribution June 4, 1993 4th Berkeley Distribution
apparently no RLIMIT_VMEM nor RLIMIT_AS. Note that on one of our AMD Linux box I see:
OK, but:
- the line mentioning RLIMIT_VMEM is commented out in the program; - if the program compiles, it means that RLIMIT_AS is indeed defined; - RLIMIT_RSS and RLIMIT_DATA should do the trick, but they do not.
PS. I'll do the tests with different compilers during the week-end.
Great. All the best,
Roberto