Hello Matt, I've started to investigate this and, at a glance, it appears to be an issue with the hdf5 library netcdf uses for netcdf-4 files. I say this based on the following stack trace: #0 0x00000001031ea430 in H5FL_arr_malloc () #1 0x0000000103299bd2 in H5S_extent_copy () #2 0x000000010329970f in H5S_copy () #3 0x000000010319ce01 in H5D__chunk_io_init () #4 0x00000001031b3536 in H5D__read () #5 0x00000001031b2fb7 in H5Dread () #6 0x00000001000694a4 in nc4_get_vara () #7 0x000000010005e4cb in NC4_get_vara () #8 0x000000010001b49a in NC_get_vara () #9 0x000000010001c264 in nc_get_vara () #10 0x00000001000077da in print_rows () #11 0x0000000100007718 in print_rows () #12 0x0000000100007222 in vardata () #13 0x0000000100004e48 in do_ncdump_rec () #14 0x0000000100003acc in main () I will continue to investigate, but I was hoping you could tell me what version of libhdf5 you are using? Thanks, have a great day, -Ward > Hello! > > I'm currently creating netCDF files (see attached example) using the C NetCDF > library. > > I can display the NetCDF header using ncdump -h, but if I try to do a full > dump it causes a Segmentation Fault partway through displaying the main > "SU_Telemetry" variable. I have tried this with both netcdf versions 4.1.3 > and 4.3.2. > > However, I can display the SU_Telemetry data array with no issues using > ToolsUI. > > I would love to write the file out so NcDump can fully display it (or at > least know why it's behaving in this way) - can you help? > > > Thanks, > Matt Wilson > > > Ticket Details =================== Ticket ID: MRV-404062 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.