Having investigated further, the problem is not actually connected to reopening of HDF5 files, and occurs, intermittently, even when I don't reopen the file and instead just re-write the entries in the data sets. I have made a build of HDF5 with its internal memory management turned off (on a different machine), and run the whole thing through with valgrind. Valgrind reports no errors (nor does hdf5), but the resulting files are (sometimes) reported as having errors when accessed afterwards either by our code or tools like h5dump.
Any suggestions as to what to try next? We have numerous various simple tests of our code that don't exhibit the problem and, so far, my attempts to produce a simpler example have not yielding something useful. Thanks very much. -- View this message in context: http://hdf-forum.184993.n3.nabble.com/reopening-for-writing-after-close-tp3942092p3971857.html Sent from the hdf-forum mailing list archive at Nabble.com. _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
