Hi again,
Mathias Wilhelm wrote:
But:
I "replaced" the
InitOnceExecuteOnce() call with boost::call_once. My test case of
writing and reading multiple HDF5 files passes without any problems, so
I anticipate that the application is thread safe, but shows a strange
behavior if only H5::H5File::isHdf5() is called:
If the application invokes H5::H5File::isHdf5() and terminates right
after it, HDF5 reports a "infinite loop closing library"[0].
If the application invokes H5::H5File::isHdf5() and opens the file for
read/write access, the application completes without any errors. The
same if H5::H5File::isHdf5() is not invoked at all.
To complete this story:
I removed the isHdf5 call in all cases and my application terminates
without any errors. I still do not know what the problem is but,
unfortunately, do not have the time to dig deeper.
I intend to test the boost::call_once hack under windows and will let
you know what the outcome is.
~Mathias
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
