Large common blocks cause SIGKILL?

[stephanjansen]

Hi,

Large common blocks cause a "Killed" message before any
code is actually executed. This happens using the em64t
version of ifort 9.0-031 on a SuSE 9.3 x86_64 machine. I'm
including a simple program that demonstrates the problem.
If I comment out the common block statement it does not
have this problem. Here's the command line output
demonstrating the problem and then the source for the
program that has the problem:

jansen-> ifort -mcmodel=large -i_dynamic t.f
jansen-> ./a.out
Killed
jansen-> cat t.f
program testing
real tmp(256,256,256,256)
common /now/ tmp

write(6,*) 'hi'

end

[Steven_L_Intel1]

Tried setting your datasize to "unlimited"? It does seem that the OS is preventing your large data size from loading.

Considered using allocatable arrays instead of COMMON?

[stephanjansen]

Hi,

Here's the output from ulimit -a:

jansen-> ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 47104
virtual memory (kbytes, -v) unlimited


The program is somewhat large and it would likely be
a pain to rewrite it avoiding the use of common blocks.
I tried using the "-dyncom" switch but that had no
effect.