diff options
| author | vchoi-hdfgroup <55293060+vchoi-hdfgroup@users.noreply.github.com> | 2023-04-13 21:36:24 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-04-13 21:36:24 (GMT) |
| commit | a66bff93b2d989f8087a9daa1ef526c8fc8b48b6 (patch) | |
| tree | 2f31d5554a62fc00b121618df41111940ab0b25d /m4 | |
| parent | 2319d4a092a2070fde91947e6a914282c676d7bf (diff) | |
| download | hdf5-a66bff93b2d989f8087a9daa1ef526c8fc8b48b6.zip hdf5-a66bff93b2d989f8087a9daa1ef526c8fc8b48b6.tar.gz hdf5-a66bff93b2d989f8087a9daa1ef526c8fc8b48b6.tar.bz2 | |
Fix for github issue #2599: (#2665) (#2706)
* Fix for github issue #2599:
As indicated in the description, memory leak is detected when running "./h5dump pov".
The problem is: when calling H5O__add_cont_msg() from H5O__chunk_deserialize(),
memory is allocated for cont_msg_info->msgs. Eventually, when the library tries to load
the continuation message via H5AC_protect() in H5O_protect(), error is
encountered due to illegal info in the continuation message.
Due to the error, H5O_protect() exits but the memory allocated for cont_msg_info->msgs is not freed.
When we figure out how to handle fuzzed files that we didn't generate,
a test needs to be added to run h5dump with the provided "pov" file.
* Add message to release notes for the fix to github issue #2599.
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions