summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLarry Knox <lrknox@hdfgroup.org>2020-08-19 20:58:33 (GMT)
committerLarry Knox <lrknox@hdfgroup.org>2020-08-19 20:58:33 (GMT)
commit4fd1958f4ca83999800deb570e20bbe940e3c047 (patch)
treeccb5ceaea2d1d1a5dbb8d3c6b3929d4149e0439d
parent0945281590c6aa715241c599ec1b1b9cd49e94a5 (diff)
parentbbc344a4f50f18b4d7c17d08ae12818b8192755e (diff)
downloadhdf5-4fd1958f4ca83999800deb570e20bbe940e3c047.zip
hdf5-4fd1958f4ca83999800deb570e20bbe940e3c047.tar.gz
hdf5-4fd1958f4ca83999800deb570e20bbe940e3c047.tar.bz2
Merging in latest from upstream (HDFFV/hdf5:refs/heads/hdf5_1_10_7)
* commit 'bbc344a4f50f18b4d7c17d08ae12818b8192755e': Disables memory sanity checks in Autotools debug builds
-rw-r--r--configure.ac7
-rw-r--r--release_docs/RELEASE.txt17
2 files changed, 19 insertions, 5 deletions
diff --git a/configure.ac b/configure.ac
index c2f5570..25ba5c0 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2555,7 +2555,8 @@ AC_ARG_ENABLE([memory-alloc-sanity-check],
more memory use and somewhat slower allocation.
This option is orthogonal to the
--enable-using-memchecker option.
- [default=yes if debug build, otherwise no]
+ [default=yes if debug build in a development
+ branch, otherwise no]
])],
[MEMORYALLOCSANITYCHECK=$enableval])
@@ -2565,11 +2566,7 @@ AC_SUBST([MEMORYALLOCSANITYCHECK])
## Set default
if test "X-$MEMORYALLOCSANITYCHECK" = X- ; then
- if test "X-$BUILD_MODE" = "X-debug" ; then
- MEMORYALLOCSANITYCHECK=yes
- else
MEMORYALLOCSANITYCHECK=no
- fi
fi
case "X-$MEMORYALLOCSANITYCHECK" in
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index 719b018..d235a66 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -47,6 +47,23 @@ New Features
Configuration:
-------------
+ - Disable memory sanity checks in the Autotools in release branches
+
+ The library can be configured to use internal memory sanity checking,
+ which replaces C API calls like malloc(3) and free(3) with our own calls
+ which add things like heap canaries. These canaries can cause problems
+ when external filter plugins reallocate canary-marked buffers.
+
+ For this reason, the default will be to not use the memory allocation
+ sanity check feature in release branches (e.g., hdf5_1_10_7).
+ Debug builds in development branches (e.g., develop, hdf5_1_10) will
+ still use them by default.
+
+ This change only affects Autotools debug builds. Non-debug autotools
+ builds and all CMake builds do not enable this feature by default.
+
+ (DER - 2020/08/19)
+
- Add file locking configure and CMake options
HDF5 1.10.0 introduced a file locking scheme, primarily to help