24.03.2014 11:00, Martijn Jasperse пишет:
Hi all,
From my experience, you cannot call H5Eget_msg while traversing the
error stack as (I think) this causes the stack to be reset. This
invalidates the current traversal and produces rubbish data after that
point. I have seen exactly the same behaviour in C with
including/excluding the H5Eget_msg call - my work-around is to record
the major/minor numbers for look-up after the stack traversal is
complete. This is somewhat undesirable and it seems unintuitive that
H5Eget_msg should fail in such a way.
Thank you for your feedback.
I propose that at least
http://www.hdfgroup.org/HDF5/doc/H5.user/Errors.html is fixed/updated
then, because now it somewhat misleading.
Best wishes,
Andrey Paramonov
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
