[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]

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.

  • Date: Fri, 02 Feb 1996 14:38:47 -0700
Hi Mike,

>       Here are the answers to your questions. I hope it helps. If you
>       can't find a solution we would think about upgrading the machine
>       to IRIX 6.1 although this has some other implications we'd rather
>       avoid. But, let me know what you find anyway. Thanks for you 
>       help ....
> 
> 
>       (1) version of netCDF 
>               - 2.4 beta 6
> 
>       (2) uname -a
>               - IRIX64 maxwell 6.0.1 12130108 IP26 mips
> 
>       (3) result of running ./configure
> 

All these look OK, and the results of your running configure exactly match
what we see on IRIX 6.1.

>       (4) result of running "make test"
 ...
> 
> making `test' in directory /vendor/netCDF/netcdf-2.4-beta6/src/ncdump
> 
> cc -o ncdump -O ncdump.o vardata.o dumplib.o ../libsrc/libnetcdf.a
>         ../ncgen/ncgen -o test0.nc -n test0.cdl
> *** Error code 139 (bu21)

Since the library tests for XDR, the netCDF C interface, and the netCDF
Fortran interface all succeed, it looks like there is an IRIX 6.0.1-specific
problem only with the ncgen utility, though we can't reproduce it here.  If
you don't need ncgen, you could assume the library is OK (it passes all the
tests), and simply use an ncgen compiled on an SGI 5.3 system, if you have
one, for example.

You might also get an ncgen utility for your system by using the "-n32" flag
to compile the library and ncgen, after setting CFLAGS to "-n32" as an
environment variable or in the CUSTOMIZE file, running the configure script
again, and rebuilding.

> maxwell 13# ./ncgen -o test0.nc -n test0.cdl
> Segmentation fault (core dumped)
> maxwell 14# dbx ./ncgen
> dbx version 6.02 Apr 21 1995 20:20:49
> Bad pc in corefile, using return address
> Core from signal SIGSEGV: Segmentation violation
> (dbx) where
> >  0 _xdr_int(0x1003b698, 0xffffffa638, 0x0, 0x1003efa0, 0x1, 0x2, 0x0, 
> > 0xfb4c460) ["/jerry/redwood/work/irix/lib/libc/libc_64mips4/rpc/xdr.c":105, 
> > 0xfb00620]
  ...
>    12 _xdr_int(0x1003b698, 0xffffffa638, 0x0, 0x1003efa0, 0x1, 0x2, 0x0, 
> 0x10013688) ["/jerry/redwood/work/irix/lib/libc/libc_64mips4/rpc/xdr.c":105, 
> 0xfb00618]

Unfortunately this doesn't pinpoint where in ncgen the problem is occurring,
and I can't reproduce the problem, so I'm stumped ...

--Russ

______________________________________________________________________________

Russ Rew                                           UCAR Unidata Program
address@hidden                              http://www.unidata.ucar.edu