summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorQuincey Koziol <koziol@hdfgroup.org>2003-10-10 15:23:38 (GMT)
committerQuincey Koziol <koziol@hdfgroup.org>2003-10-10 15:23:38 (GMT)
commitd04ba65f9d10799009a9da3471ec7edd9becee7c (patch)
treeb1093be3d5286a0c03b814f93d807c5a2206720b
parent421dfab94c830224e04955e7fabe9d65a6e6e35a (diff)
downloadhdf5-d04ba65f9d10799009a9da3471ec7edd9becee7c.zip
hdf5-d04ba65f9d10799009a9da3471ec7edd9becee7c.tar.gz
hdf5-d04ba65f9d10799009a9da3471ec7edd9becee7c.tar.bz2
[svn-r7593] Purpose:
Bug fix Description: The 'char *' type is one of the "strongly" aligned types on Crays, but a 'void *' is "weakly" aligned. So, assigning a 'void *' (pointing to a location to place a 'char *') to a 'char **' can change the pointer value during the assignment. Solution: Don't alias the 'void *' where the variable-length information ('char *' or 'hvl_t') will go. Use a temporary variable on the stack to build up the information about the VL string or sequence and then memcpy() the temporary variable directly to the location pointed to with the 'void *' Platforms tested: FreeBSD 4.9 (sleipnir) Cray SV1 (wind) specific to Cray problems, h5committest not necessary.
-rw-r--r--release_docs/RELEASE.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index 5adcb91..619be24 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -60,6 +60,8 @@ Bug Fixes since HDF5-1.6.0 release
Library
-------
+ - Fixed problems with accessing variable-length data datatypes on
+ Crays. QAK - 2003/10/10
- Fixed potential file corruption bug when too many object header
messages (probably attributes, from a user perspective) were
inserted into an object header and certain other conditions were