summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDana Robinson <derobins@hdfgroup.org>2016-03-23 20:26:53 (GMT)
committerDana Robinson <derobins@hdfgroup.org>2016-03-23 20:26:53 (GMT)
commit674385b72e1987f68e27504b8224c60706d5b835 (patch)
tree7908d824bd05386b4780b1ccbb71a8e53e8a74db
parent0b4a9dcbfaf63edef0ce391091a281a778035230 (diff)
downloadhdf5-674385b72e1987f68e27504b8224c60706d5b835.zip
hdf5-674385b72e1987f68e27504b8224c60706d5b835.tar.gz
hdf5-674385b72e1987f68e27504b8224c60706d5b835.tar.bz2
[svn-r29542] Updated known problems section in RELEASE.txt.
-rw-r--r--release_docs/RELEASE.txt17
1 files changed, 13 insertions, 4 deletions
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index ac504ce..5e5f3a8 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -591,14 +591,23 @@ known issues if it is a new issue.
(ADB - 2016/03/22, HDFFV-9734)
- The flush/refresh test occasionally fails on OS X platforms. This is
- being investigated and may be a problem with SWMR on HFS+.
+ being investigated but no fix or workaround is available at this time.
(DER - 2016/03/22, HDFFV-9731)
- The VDS/SWMR test will fail with a segmentation fault if the library
- is built with --enable-using-memchecker.
+ is built with --enable-using-memchecker. The is due to a VDS shutdown
+ procedure freeing a shared resource too early when the memory
+ checker changes are built. This problem does not arise when the
+ memory checker changes are not used since the internal library free
+ lists behave differently. The memory checker configure option should
+ normally only be used under special circumstances so this should not
+ affect most users. Users should be aware that the --enable-using-memchecker
+ + VDS combination may cause a segfault, however, so Valgrind et al. may
+ have to be used with an HDF5 library built without the feature if this
+ proves to be a problem.
(DER - 2016/03/21, HDFFV-9732)
- - SWMR feature
+ - SWMR feature limitations
The SWMR feature will only work if an HDF5 file under SWMR access resides
on a file system that obeys POSIX write() ordering semantics. Because of
this, SWMR will not work on network file systems such as NFS or SMB/Windows
@@ -609,7 +618,7 @@ known issues if it is a new issue.
obvious reasons for it to not work on NTFS or GPFS.
(EIP - 2016/03/20, HDFFV-9733)
- - VDS feature
+ - VDS feature limitation
Currently, the path to a VDS source file is interpreted as relative to the
directory where the executable program runs and not to the HDF5 file with
the VDS dataset unless a full path to the source file is specified during