diff options
| author | Vailin Choi <vchoi@hdfgroup.org> | 2020-04-02 03:14:42 (GMT) |
|---|---|---|
| committer | Vailin Choi <vchoi@hdfgroup.org> | 2020-04-02 03:14:42 (GMT) |
| commit | bae05235a2d87acb0d6b3a2e1c32f3b6f48cf203 (patch) | |
| tree | fcd82c20fec3b44713680b676e499080df991afc /test/flush2.c | |
| parent | 281e8444d862991aeca1a28e42e387a627bc362b (diff) | |
| parent | afdcac28b85d690eebc80ab568fa5266081baaaa (diff) | |
| download | hdf5-bae05235a2d87acb0d6b3a2e1c32f3b6f48cf203.zip hdf5-bae05235a2d87acb0d6b3a2e1c32f3b6f48cf203.tar.gz hdf5-bae05235a2d87acb0d6b3a2e1c32f3b6f48cf203.tar.bz2 | |
Merge pull request #2461 in HDFFV/hdf5 from ~VCHOI/my_third_fork:bugfix/dtype_close_on_error to develop
* commit 'afdcac28b85d690eebc80ab568fa5266081baaaa':
A fix in the cleaning up code for datatype when datatype initialization via H5D__init_type() fails. This is triggered by the tests for revised references when the libver bounds setting does not allow version 4 datatype message to be created. The test failure is abort core dumped. This is due to the datatype initialization fails before the datatype ID is registered. The datatype cleanup code should provide for the above situation. The code to fix the problem is the same as what is done in H5D__open_oid().
Diffstat (limited to 'test/flush2.c')
0 files changed, 0 insertions, 0 deletions