Update RELEASE.txt to correct merge problems and text formatting.

1 files changed, 25 insertions, 23 deletions

diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index 9d6cf36..719b018 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -379,25 +379,36 @@ Bug Fixes since HDF5-1.10.6 release
     - Fixed issues CVE-2018-13870 and CVE-2018-13869
 
       When a buffer overflow occurred because a name length was corrupted
-      threads is high (>16 threads).  The problem was due to the file pointer that
-      was set in the variable length string datatype for the attribute.  That file
-      pointer was already closed when the attribute was accessed.
+      and became very large, h5dump crashed on memory access violation.
 
-      The problem was fixed by setting the file pointer to the current opened file pointer
-      when the attribute was accessed.  Similar patch up was done before when reading
-      dataset with variable length string datatype.
+      A check for reading past the end of the buffer was added to multiple
+      locations to prevent the crashes and h5dump now simply fails with an
+      error message when this error condition occurs.
+
+      (BMR - 2020/7/31, HDFFV-11120 and HDFFV-11121)
+
+    - Fixed the segmentation fault when reading attributes with multiple threads
+
+      It was reported that the reading of attributes with variable length string
+      datatype will crash with segmentation fault particularly when the number 
+      of threads is high (>16 threads).  The problem was due to the file pointer 
+      that was set in the variable length string datatype for the attribute.  
+      That file pointer was already closed when the attribute was accessed.
+
+      The problem was fixed by setting the file pointer to the current opened 
+      file pointer when the attribute was accessed.  Similar patch up was done 
+      before when reading dataset with variable length string datatype.
 
       (VC - 2020/07/13, HDFFV-11080)
 
     - Fixed CVE-2018-17435
 
-      The tool h52gif produced a segfault when the size of an attribute
-      message was corrupted and caused a buffer overflow.
+      The tool h52gif produced a segfault when the size of an attribute message 
+      was corrupted and caused a buffer overflow.
 
-      The problem was fixed by verifying the attribute message's size
-      against the buffer size before accessing the buffer.  h52gif was
-      also fixed to display the failure instead of silently exiting
-      after the segfault was eliminated.
+      The problem was fixed by verifying the attribute message's size against the 
+      buffer size before accessing the buffer.  h52gif was also fixed to display
+      the failure instead of silently exiting after the segfault was eliminated.
 
       (BMR - 2020/6/19, HDFFV-10591)
 
@@ -529,7 +540,7 @@ Bug Fixes since HDF5-1.10.6 release
       (DER - 2019/09/17, HDFFV-10893)
 
     - Don't allocate an empty (0-dimensioned) chunked dataset's chunk
-        index, until the dataset's dimensions are increased.
+      index, until the dataset's dimensions are increased.
 
       (QAK - 2020/05/07)
 
@@ -672,7 +683,7 @@ Bug Fixes since HDF5-1.10.6 release
 
     Testing
     -------
-    -  Stopped java/test/junit.sh.in installing libs for testing under ${prefix}
+    - Stopped java/test/junit.sh.in installing libs for testing under ${prefix}
 
       Lib files needed are now copied to a subdirectory in the java/test
       directory, and on Macs the loader path for libhdf5.xxxs.so is changed
@@ -884,15 +895,6 @@ The include folder holds the header files and the fortran mod files. CMake
 the share folder.
 
 The bin folder contains the tools and the build scripts. Additionally, CMake
-creates dynamic versions of the tools with the suffix "-shared". Autotools
-installs one set of tools depending on the "--enable-shared" configuration
-option.
-  build scripts
-  -------------
-  Autotools: h5c++, h5cc, h5fc
-  CMake: h5c++, h5cc, h5hlc++, h5hlcc
-
-The include folder holds the header files and the fortran mod files. CMake
 places the fortran mod files into separate shared and static subfolders,
 while Autotools places one set of mod files into the include folder. Because
 CMake produces a tools library, the header files for tools will appear in