Quincey wrote: > but you probably want to use the H5Lexists() routine for this sort of check.
On 2011-01-27 15:12, Binh-Minh Ribler wrote: > If you continue using your current approach, you will need fg_p to be of type > Group so that the correct exception, GroupIException, would be thrown. Hi, I think I will use the C API function thank you both for pointing this out. But I still don't get the current behaviour. I try to catch any FileIException, which is thrown according to: "terminate called after throwing an instance of 'H5::FileIException'" The backtrace is: (gdb) bt #0 0x92525e42 in __kill () #1 0x92525e34 in kill$UNIX2003 () #2 0x9259823a in raise () #3 0x925a4679 in abort () #4 0x91c69005 in __gnu_cxx::__verbose_terminate_handler () #5 0x91c6710c in __gxx_personality_v0 () #6 0x91c6714b in std::terminate () #7 0x91c67261 in __cxa_throw () #8 0x0133dbe6 in H5::H5File::throwException () #9 0x016a4454 in H5::CommonFG::openDataSet () #10 0x016a4582 in H5::CommonFG::openDataSet () So obviously H5File throws a FileIException indeed in its overloading of CommonFG's abstract throwException(). One possibility to explain the issue may be dynamic linking problems, maybe, so that the type checking during the catch phase wrongly does not recognize the correct catch clause. I will look more into this direction now. Greetings, Daniel
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
