NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Ed,
I've found the problem in nc4df.c around line 3647:
if (!(h5dimlen = nc_malloc(var->ndims * sizeof(hsize_t))))
return NC_ENOMEM;
it is possible that var->ndims==0 at this point which causes malloc to
return 0 and netcdf to return NC_ENOMEM.
On Wed, Jan 20, 2010 at 2:14 PM, Jim Edwards <jedwards@xxxxxxxx> wrote:
> I don't - so far I've traced the problem to the call to
> if ((retval = nc4_rec_match_dimscales(nc->nc4_info->root_grp)))
>
> at around line 1856 of file nc4file.c
>
>
>
>
> On Wed, Jan 20, 2010 at 2:12 PM, Ed Hartnett <ed@xxxxxxxxxxxxxxxx> wrote:
>
>> Jim Edwards <jedwards@xxxxxxxx> writes:
>>
>> > Hi Ed,
>> >
>> > I built with --enable-logging but I'm not finding any logs - did I miss
>> > something?
>> >
>>
>> No, it doesn't give you log output unless you put in a call to
>> nc_set_log_level(3)
>>
>> But even without doing that it will print out the HDF5 error stack
>> whenever netCDF-4 encounters a HDF5 error. So rerun your program and see
>> if you get an output about the error.
>>
>> Thanks,
>>
>> Ed
>> --
>> Ed Hartnett -- ed@xxxxxxxxxxxxxxxx
>>
>
>
netcdfgroup archives: