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

[netCDF #UBS-599337]: Abort on reading damaged HDF5 file

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: [netCDF #UBS-599337]: Abort on reading damaged HDF5 file
  • Date: Mon, 15 May 2017 12:32:34 -0600
Took a quick look. This code duplicates code in libdispatch/dfile.c
except that nc4file.c uses HDF5is_hdf5() function.
What this means is that the NC_check_file_type code in dfile.c
is saying the file is an HDF5 file, hence it set the dispatch table
to use libsrc4. However, the later call to nc_check_for_hdf() in ncfile.c
says it is not an HDF5 file. So, there is a bigger problem here.
My immediate speculation is that HDF5is_hdf5() is testing something more
than what what is being tested in NC_check_file_type().

What version of HDF5 library are you using?

=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: UBS-599337
Department: Support netCDF
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.