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.
Paul, >Date: Wed, 12 Jul 2000 11:58:24 -0400 >From: Paul van Delst <address@hidden> >Organization: CIMSS @ NOAA/NCEP >To: Steve Emmerson <address@hidden> >Subject: Re: 20000711: Run time array bounds error in netCDF3.5_beta (fwd) >Keywords: 200007121558.e6CFwPT11383 In the above message, you wrote: > O.k., I added the following to the configure file: > > CC=/bin/xlc > FC=/bin/xlf > F90=/bin/xlf90 > FFLAGS=${FFLAGS--g -C} > F90FLAGS=${F90FLAGS--g -C -qsuffix=f=f90} > > I then did a "make clean" and a "make distclean" and confirmed that > "config.cache" did not exist. > > $ ./configure >> configure.log 2>>configure.log > > Appeared to work just fine > > > $ make >> make.log 2>>make.log > > Also worked fine. > > > $ make test >> test.log 2>>test.log > > Failed but apparently because there is an errant "-c" switch in the > execution statement for nf_test. > > > I then went into the nf_test directory and ran the program manually: > > $ dbx nf_test > Type 'help' for help. > reading symbolic information ... > (dbx) run > *** Testing nf_strerror ... > *** Testing nf_open ... > *** Testing nf_close ... > *** Testing nf_inq ... > *** Testing nf_inq_dimid ... > *** Testing nf_inq_dim ... > size unexpected: 0 > > ### 1 FAILURES TESTING nf_inq_dim! ### > *** Testing nf_inq_dimlen ... > size unexpected: 0 > > ### 1 FAILURES TESTING nf_inq_dimlen! ### > *** Testing nf_inq_dimname ... > *** Testing nf_inq_varid ... > *** Testing nf_inq_var ... > *** Testing nf_inq_natts ... > *** Testing nf_inq_ndims ... > *** Testing nf_inq_nvars ... > *** Testing nf_inq_unlimdim ... > *** Testing nf_inq_vardimid ... > *** Testing nf_inq_varname ... > *** Testing nf_inq_varnatts ... > *** Testing nf_inq_varndims ... > *** Testing nf_inq_vartype ... > *** Testing nf_get_var1_text ... > unexpected: 0.000000000000000000E+00 > nf_get_var: Index exceeds dimension bound > nf_get_var: Index exceeds dimension bound > unexpected: 0.000000000000000000E+00 > unexpected: 0.000000000000000000E+00 > unexpected: 0.000000000000000000E+00 > > Trace/BPT trap in util.hash at line 397 in file "util.F" > 397 result = base * (result + index(d) - 1) > > > Is this info any more helpful? Yes. Thanks. I've fixed the bounds-checking problems that emerge when the native AIX Fortran compiler is used with the "-C" option. The changes will be in the next release. The bugs would not cause the current release to be incorrect -- so you're OK. Regards, Steve Emmerson <http://www.unidata.ucar.edu>