This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>To: address@hidden >From: Kate Hedstrom <address@hidden> >Subject: f90 on Cray T3E >Organization: UCAR/Unidata >Keywords: 200111161935.fAGJZwN14729 Kate, > Well, that sure got a different response: > > SIGNAL: Floating point exception (invalid floating point operation) > > Beginning of Traceback (PE 0): > Interrupt at address 0x80011da9c in routine 'ncx_put_float_double'. > Called from line 3600 (address 0x800123c3c) in routine > 'ncx_putn_float_double'. > Called from line 975 (address 0x800112184) in routine > 'ncx_pad_putn_Idouble'. > Called from line 2123 (address 0x800114ba4) in routine 'nc_put_att_double'. > Called from line 117 (address 0x80014e2d0) in routine 'NF_PUT_ATT_REAL'. > Called from line 244 (address 0x8000090dc) in routine > 'NF90_PUT_ATT_FOURBYTEREAL_in_NETCDF'. > Called from line 51 (address 0x800001fa8) in routine 'NETCDFTEST'. > Called from line 475 (address 0x800000c94) in routine '$START$'. > End of Traceback. > sh: 50567 Floating exception(coredump) > > > Do you want any more information? Oops, offhand I don't know why this floating exception occurred. Maybe it's an alignment problem in the underlying C library. being asked to store a 4-byte float that's not 8-byte aligned. If there's any way you can turn off alignment checks or make them less strict, that might be a workaround. I'm afraid I'm on vacation until Monday, November 26, so this one might have to wait awhile, since Steve Emmerson is also away from the office. You might send the problem to Robert Pincus <address@hidden> to see if he has any ideas ... --Russ