[netCDF #RUF-772159]: group name as const char* in nc_def_grp

> > BTW, do you have any idea why netCDF 4.1 can generate an invalid HDF 5 
> > file sometimes? I have encountered this problem in my code, but I 
> > cannot reproduce it using simpler codes. So I didn't formerly report 
> > the bug. (My code checks the return status in every netCDF call, and 
> > there is no complain from netCDF at all.) In the end, I get around the 
> > problem by changing the order of defining variables.
 ...
> Indeed, none of the scenarios applies. But I don't know how to 
> demonstrate the bug in a simple way. (My code is too involved to show 
> the case.) If I provide you with the corrupted HDF 5 file, will you be 
> able to tell what went wrong? Thanks.

No, sorry, that wouldn't help as far as I know.  If you ever encounter a 
reproducible demonstration of the bug, please let us know.

--Russ


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



Ticket Details
===================
Ticket ID: RUF-772159
Department: Support netCDF
Priority: High
Status: Closed