When a high resolution calculation is performed, a segmentation fault might be caused according to version of OS and kernel.
In this case, there is a possibility that the maximum value of the use capacity of a stack area of the memory is set comparatively small.
In many cases, the maximum value of this use capacity is the one that is called "soft limit" that users can set. Therefore, it can be set that the maximum value is increased as follows. However, a soft limit cannot be greatly set more than a "hard limit" that is the maximum value that has been decided on the system side.
A hard limit of a stack area is examined as follows.
> limit -h | grep stack stacksize XXXXXXXX
"XXXXXXXX" is a value of a hard limit. (Numerical value or "unlimited" is displayed). This "XXXXXXXX" is set to a soft limit of a stack area as follows.
> limit stacksize XXXXXXXX
A hard limit of a stack area is examined as follows.
$ ulimit -Ha |grep stack stack size (kbytes, -s) XXXXXXXX
"XXXXXXXX" is a value of a hard limit. (Numerical value or "unlimited" is displayed). This "XXXXXXXX" is set to a soft limit of a stack area as follows.
$ ulimit -s XXXXXXXX
A part of NAMELIST group name is not loaded in rare cases when a lot of NAMELIST group names is described in a file.
Please check messages output by an execution program when information of NAMELIST is not reflected in the execution program though it is sure to be written in the file correctly. The symptom described in the above-mentioned will appear if following messages are displayed.
!*** WARNING [XxxxNmlRead] *** NAMELIST group "xxxx_nml" is not found
in "xxxx_xxxx.nml" (iostat=190).
^^^^^^^^^^ This is the feature.
In this case, please insert some null lines or comment lines in front of the NAMELIST, and check operation with repeated execution of the program. The above-mentioned symptom seems to be evaded by some null lines or comment lines. (The cause is uncertain).
