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

Re: Problem with nccreate

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.

  • Subject: Re: Problem with nccreate
  • Date: Fri, 23 Sep 1994 15:16:38 -0600
> Organization: NOAA/FSL
> Keywords: 199409231433.AA02505

Hi Linda,

> I am having problems with the nccreate command.  It is invoked with the
> following command:
> 
>    cdfid = nccreate(fname, NC_CLOBBER);  /* returns -1 if error */
>  
> I have verified that fname is a proper file name.  it is also opening the
> file is the same directory as the code is located.
> 
> The result is the following message when I run it in dbx:
> 
>    signal SEGV (no mapping at the fault address) in malloc at 0xf76b45d4
>    malloc+0xf0:       ld      [%i3 + 12], %i5
> 
> Any ideas?

This doesn't look like a netCDF problem, but rather a problem with fname not
being null-terminated (are you sure when you malloced space for it you got
enough space for the null byte that terminates the string?) or with a
previous pointer problem causing something to be overwritten.  The latter
kind of problem can be found with tools such as Centerline, ObjectCenter,
Purify, or the new runtime memory access checking in the new Solaris version
of dbx.

--
Russ Rew                                                UCAR Unidata Program
address@hidden                                          P.O. Box 3000
http://www.unidata.ucar.edu/                          Boulder, CO 80307-3000