summaryrefslogtreecommitdiffstats
path: root/test/tbad_msg_count.h5
diff options
context:
space:
mode:
authorQuincey Koziol <koziol@hdfgroup.org>2008-01-13 05:38:40 (GMT)
committerQuincey Koziol <koziol@hdfgroup.org>2008-01-13 05:38:40 (GMT)
commit52e401106794acc8ca9f654e8c9d22159f4e9bab (patch)
treec186de5724d9b25c9f95b0de440d3806862baf00 /test/tbad_msg_count.h5
parentfc59a903d181253c43444ae1d1dd5de4692f8dc0 (diff)
downloadhdf5-52e401106794acc8ca9f654e8c9d22159f4e9bab.zip
hdf5-52e401106794acc8ca9f654e8c9d22159f4e9bab.tar.gz
hdf5-52e401106794acc8ca9f654e8c9d22159f4e9bab.tar.bz2
[svn-r14403] Description:
Add work-around to allow reading files that were produced with a buggy earlier version of the library, which could create objects with the wrong object header message count. There is now a configure flag "--enable-strict-format-checks" which triggers a failure on reading a file with this sort of corruption (when enabled) and allows the object to be read (when disabled). The default value for the "strict-format-checks" flag is yes when the "debug" flag is enabled and no when the "debug" flag is disabled. Note that if strict format checks are disabled (allowing objects with this particular kind of corruption to be read) and the file is opened with write access, the library will re-write the object header for the corrupt object with the correct # of object header messages. This closes bugzilla bug #1010. Tested on: Linux/32 2.6 (kagiso) FreeBSD/64 6.2 (liberty)
Diffstat (limited to 'test/tbad_msg_count.h5')
-rw-r--r--test/tbad_msg_count.h5bin0 -> 1984 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/test/tbad_msg_count.h5 b/test/tbad_msg_count.h5
new file mode 100644
index 0000000..ca5eb65
--- /dev/null
+++ b/test/tbad_msg_count.h5
Binary files differ