diff options
author | David Young <dyoung@hdfgroup.org> | 2020-03-12 19:00:07 (GMT) |
---|---|---|
committer | David Young <dyoung@hdfgroup.org> | 2020-03-12 19:00:07 (GMT) |
commit | 7613f7e1aa89210bb625d59d79a6220c49a1f22c (patch) | |
tree | ea9ec922ecee66b45b90e5cd2024332930fcf1f0 /m4 | |
parent | 9abbdeaa66c70a00b6a7bedee9c76d2493a8e947 (diff) | |
parent | 093c2c7e69bc4a40e9d49eece1d6fdcf54e8ecb0 (diff) | |
download | hdf5-7613f7e1aa89210bb625d59d79a6220c49a1f22c.zip hdf5-7613f7e1aa89210bb625d59d79a6220c49a1f22c.tar.gz hdf5-7613f7e1aa89210bb625d59d79a6220c49a1f22c.tar.bz2 |
Merge pull request #2378 in HDFFV/hdf5 from ~DYOUNG/werror:dont-crash-on-close to develop
* commit '093c2c7e69bc4a40e9d49eece1d6fdcf54e8ecb0':
Avoid a crash, don't check if we're flushing when the file is closing: there's no need to check if the metadata cache is flushing if we already know the file is closing, because the condition we rely on is "closing OR flushing." Further, the cache may have already gone away, so sometimes calling into the cache to see if it's flushing will crash the program.
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions