ENTRY bug

[Steve Kargl]

Gang,

1) I can't distribute the code that a colleague gave me.
2) It's over 190000 lines of some of the ugliest Fortran code
   that I've seen.  The build infrastructure is even worse.
   I don't know if I'm going to be able to reduce this to
   a manageable case. :(
3) g77 compiles the code fine.
4) gfortran compiles the code, but we die with

Program terminated with signal 11, Segmentation fault.
#0  master.0.str_eig (__entry=1, edfndxe=0x0, nrngv=0x0, nbrnv=0x0, 
    rblke=0xbff6d938, iblke=0xbff7293c, edfnum=0xbff77aa0, eignam=0x8326690, 
    _eignam=8) at str_eig.f:179
179            END
(gdb) bt
#0  master.0.str_eig (__entry=1, edfndxe=0x0, nrngv=0x0, nbrnv=0x0, 
    rblke=0xbff6d938, iblke=0xbff7293c, edfnum=0xbff77aa0, eignam=0x8326690, 
    _eignam=8) at str_eig.f:179
#1  0x08155194 in lst_blk_ (eignam=0x8326690, edfnum=0xbff77aa0, 
    iblke=0xbff7293c, rblke=0xbff6d938, _eignam=8) at str_eig.f:137
#2  0x0811c7d2 in cmp_eig5_ () at cmp_eig5.f:293
#3  0x08077dd4 in cmp_eig_ () at cmp_eig.f:78
#4  0x08070fb5 in prc_cmd_ () at prc_cmd.f:264
#5  0x08049332 in prc_crd_ () at prc_crd.f:105
#6  0x0804868f in cass_v3_ () at cass_v4.f:168
#7  0x080482be in MAIN__ () at Main.f:17
#8  0x081f0f17 in main (argc=Cannot access memory at address 0x0
) at ../../../gcc4x/libgfortran/fmain.c:18

Consider this a heads up.  If any one knows how to write tortorous
Fortran code with ENTRY statements, there's a bug that you can trigger.

-- 
Steve