| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
H5HG_load made improper assumptions about the ordering of object indices, namely
that they are in order. Not only is this not guaranteed by the file format
spec, but this condition can be violated if id's "wrap around" which can happen
when overwriting VL data. H5HG_load has been fixed to handle any order of
indices. Also fixed some other bugs involving allocation of global heaps in
memory.
Tested: jam, linew, amani (h5committest)
|
|
|
|
|
|
|
|
|
| |
Description:
Calling H5Tcommit on a file with read only access would cause an
assertion failure. Added a check to H5T_commit to return a failure in
this case.
Tested: jam (very minor change)
|
|
|
|
|
|
|
|
| |
added a signal handler to the tcheck_version to intercept the abort signal from
H5check_version. Some systems would prints extra messages and/or core dump if
the abort signal is not handled. This eliminates those unwanted side effect.
Tested: h5committested.
|
|
|
|
|
|
|
| |
Added EXIT_SUCEESS and EXIT_FAILURE macro values test.
Tested:
h5committested.
|
|
|
|
|
|
|
|
|
| |
There was a typo in the H5Pget_preserve that it was returning the wrong value.
Fixed. Also added a test in test/cmpd_dset.c to verify the correctness of
H5Pset_preserve and H5Pget_preserve.
Tested:
h5committest plus jam serial.
|
|
|
|
| |
Tested: Jam.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Embed the content of libhdf5.settings into the hdf5 executables so that an
"orphaned" executables can display (via the Unix strings command, for example)
the library settings used to build the executables.
configure.in:
Added the --disable-embedded-libinfo option to disable this feature.
configure:
src/H5config.h.in:
fortran/configure
c++/configure
Generated by autotools like automake.
src/H5detect.c:
Implement insert_libhdf5_settings() to insert the contents of
libhdf5.settings into the library as an extern string variable so that it
is included in all HDF5 executable.
test/Makefile.in:
Added test scripts testlibinfo.sh and testcheck_version.sh, test program
tcheck_version. Needed to introduce $PROGS so that tcheck_version is
built but not run automatically.
test/testlibinfo.sh.in:
A new test added to verify the library information is indeed included
in the executables.
H5.c: added code to print the embedded library information when there is
a library versions mis-match occurs. This ensures the library information
string is included in the executable.
Also modifies the code so that the Library mismatch warning string is
included only once in the executable.
H5private.h:
Added a global reference to the libinfo string variable to prepare
for possible stage 3 implementation of a public API.
New test: (Bug ID 1656):
Add new tests (tcheck_version, testcheck_version.sh) to verify H5check_version()
does issue warnings and abort accordingly.
Changed H5check_version() to suppress the warning message totally if
$HDF5_DISABLE_VERSION_CHECK is 2 or higher. (Old behavior treated 3 or higher
the same as 1, that is to print a warning and allows the program to continue.
MANIFEST:
updated with the newly added files.
Tested:
h5committest passed. Also passed jam in serial mode, --enable-static-exec,
--disable-embedded-libinfo.
|
|
|
|
|
|
|
|
|
|
|
| |
Add backward compatibility test to make certain that the 1.6 library
handles encountering a file with a fixed array chunk index gracefully.
Also, remove the (generated) testh5ls.sh at 'make distclean'
Tested on:
FreeBSD/32 6.3 (duty) w/production
(too minor to require h5committest)
|
|
|
|
|
|
|
|
|
| |
library works correctly
because fill value is written to the attribute during H5A_close if no data is written.
v1.8 and later leaves it empty.
Tested on jam - simple change for test.
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
Previously, when H5Z_filter_info was called for a filter that was not present,
it would succeed and return the information from one position past the end of
the pipeline, possibly causing a segfault. This affected at least
H5Pget_fitler_by_id, and possibly other API functions. Fixed to properly
return failure.
Tested: jam
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
When using H5T_copy on committed datatypes that are already open, H5T_copy would
properly use the already existing shared struct, but would still deep copy all
of the fields in that struct. This would cause memory leaks, and in the case of
a compound containing a vlen (or reference), the change in size would cause the
size of the resulting type to be set to an incorrect value. Changed H5T_copy to
properly avoid deep copies when using a reopened shared struct.
Tested: jam, linew, smirom (h5committest)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
directory directly and opened
the file with write mode. The file could be modified potentially. I changed it to make
a copy of the source file in the build directory. I also renamed the data file from
family_v1.7_0000[0-3].h5 to family_v1.8_0000[0-3].h5.
Tested on jam - I've tested the changes in v1.8 using h5committest.
|
|
|
|
|
|
|
|
| |
Description:
Versioning was just added to H5Z_class_t in 1.8. Therefore, I am adding a H5Z_class1_t
macro to 1.6 to enable backwards compatibility using H5Z_class1_t.
Tested: jam (simple change)
|
|
|
|
|
|
|
|
| |
Open the file twice to make
sure the superblock isn't corrupted.
Tested on jam - simple test.
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
The meaning of the "nbytes" field in H5D_rdcc_t was not clear, and some places
assumed it was the maximum size of the chunk cache, while some assumed it was
the current size of the chunk cache. The end result was that only 1 chunk could
be held in cache at a time. This field has been replaced by "nbytes_max" and
"nbytes_used". Performance of cached I/O should improve greatly.
Tested: jam, smirom (h5committest)
|
|
|
|
| |
tested: windows, linux (split, sec2)
|
|
|
|
|
|
|
|
|
|
| |
framework
Call h5_fixname (with an array of test filenames) for generating the
filename to create and then call h5_cleanup() when the tests pass, to delete the files
created and close the FAPL from h5_fileaccess().
tested: windows, linux
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
framework
use a fapl obtained by h5_fileaccess to the call of H5Fcreate
and redo the test calls with
h5_reset();
fapl = h5_fileaccess();
nerrors += do_ranks( fapl ) < 0 ? 1 : 0;
nerrors += test_external( fapl ) < 0 ? 1 : 0;
nerrors += do_layouts( fapl ) < 0 ? 1 : 0;
tested: windows, linux
|
|
|
|
|
|
| |
Changed 'THG' to 'The HDF Group' in various HDF5 source files,
most of which are <subdirectory>/COPYING.
-- Closes Bugzilla entry 1403.
|
|
|
|
|
|
|
|
| |
definition of an array in H5D_istore_initialize_by_extent, causing an iteration to continue and an assertion in H5S_hyper_iter_init when trying to initialize a non existing chunk.
Added a test for shrinking to 0 dimemsions
Tested: windows, linux
|
|
|
|
|
|
|
|
| |
Bug fixes: chunks on the btree were not deleted for the case when the new dimension was on the boundary of the chunk offset (comparison of offset > chunk instead of offset >= chunk). In extending the space, the new size was wrongly compared with the maximum extend possible
Modified H5Dset_extent so that it fails when called for compact datasets and contiguous with no external storage
new test program as 1.8 and 1.9: It adds tests for several ranks, use of fill value or not, compression, different fill value allocation times, use of different storage layouts, and external files
tested: windows, linux
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: The h5perf tool was getting installed in 1.8 and 1.9, but
not in 1.6.
Added a line to perform/Makefile.in to ensure that h5perf
is installed in 1.6.
Also added a line to test/Makefile.in, adding an install target
which will build all tests (equivalent to 'make all'). H5perf
needs the test library built, but doing a 'make install'
from the top level would fail in the perfom directory because
nothing would happen upon recursing into the test directory.
Tested: kagiso, jam, smirom, liberty
|
|
|
|
|
|
|
| |
Decription: Added macros defining the "1" version functions in the 1.6 branch.
Added tests for these macros. Closes bug 1318.
Tested: kagiso, linew, smirom (h5committest)
|
|
|
|
|
|
|
| |
Solution:
Check for the existence of chunks before pruning them (an assertion was triggered when attempting to do so)
Tested: windows , linux, solaris
|
|
|
|
|
|
|
|
| |
HDF5 library. The Dependencies files are generated by
"make depend".
Tested:
h5committest, also serial in Kagiso is tested.
|
|
|
|
|
|
|
|
| |
H5Fget_obj_count to ssize_t and modified
C++ and Fortran API functions. This is for bug #1245.
Tested on kagiso - I've tested the same change for the trunk using h5committest.
|
|
|
|
|
|
|
|
|
| |
correctly with nested
compound datatype. The size of compound type's member type wasn't updated. It's
fixed in this commit.
Tested on smirom. The same change was tested on three systems for v1.9.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
On Windows, certain users were having trouble with the "ohdr" test, which does some processing on object header messages. The errors were hard to reproduce on our machines, and we eventually determined that the errors were timezone-specific.
The bug is triggered on Windows when processing timestamps very near the "Epoch" (midnight on 1/1/1970)-- the mktime() function does some automatic adjustment on the time to correct for timezones. In the USA, the correction adds a few hours; in Europe, it subtracts, thus giving us times pre-Epoch.
This only affects Windows because the Windows mktime() function cannot handle times before 1970-- other systems seemingly can.
The fix is to simply create timestamps only as early as 01/02/1970. This way, any timezone adjustment will still be post-Epoch.
This bug only affects the ohdr test, and shouldn't be a problem in the library. The earliest timestamps that will actually be read will be around the time HDF5 was created (~1996-7, per Quincey).
Tested:
h5committest (kagiso, linew, smirom)
|
|
|
|
|
|
|
|
|
| |
Description: cleaning up configure related to removal of --disable-hsizet
flag, which we no longer support. Furthermore, the
H5_HAVE_LARGE_HSIZET macros in the source code have been
removed.
Tested: kagiso
|
|
|
|
|
|
|
|
|
|
| |
Bug fix.
The flush1/fflush1 test must be done before flush2/fflush2 should
be run. Added a dependance to enforce it.
Tested: kagiso. (no committest since it is a simple change. If it works
for one, it should work for all.)
|
|
|
|
|
|
|
|
| |
failure in the test, it may be easier
to reproduce the problem.
Tested on kagiso. Simple change.
|
|
|
|
|
|
|
|
| |
H5Sselect_hyperslab, for both chunked and
contiguous datasets.
Tested on smirom, kagiso, and linew.
|
|
|
|
|
|
|
|
| |
identifier returned by H5Rdereference. The function would not be able to determine a valid object name.
Fixed it and added some tests in getname.c.
Tested on smirom, kagiso, and linew.
|
|
|
|
|
|
|
|
| |
Change the 'coord' parameter for H5Sselect_elements() from 'hsize_t **' to
'hsize_t *' in this branch also.
Tested on:
Mac OS X/32 10.5.1 (amazon)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
| |
The object file tcoords.o and
tcoords.lo weren't cleaned by "gmake clean". Corrected it.
Tested on smirom. Simple change.
|
|
|
|
|
|
|
|
| |
caused a failure for PGI
compilers.
Tested on smirom with PGI compiler. Simple change.
|
|
|
|
| |
Tested on smirom.
|
|
|
|
|
|
|
|
| |
H5Sselect_hyperslab for test
purpose.
Tested on smirom only. Simple changes.
|
|
|
|
|
|
|
|
|
|
| |
dataspace selection went wrong when
the selection of some dimensions are full and these dimensions are optimized through
"flattenning". The calculation of the coordinates wasn't general enough in H5Shyper.c. Also
added a test program for it.
Tested on smirom only because the same code was tested on 3 platforms for v1.8.
|
|
|
|
| |
removing the stream-vfd.
|
|
|
|
|
|
|
| |
Removed the stream-vfd from the basic library code.
Platforms tested:
Kagiso (serial and parallel).
|
|
|
|
|
|
|
|
|
|
| |
Back-port change of semantics for constant messages (to allow them to be
deleted, but not modified) from the 1.8 branch.
Tested on:
Mac OS X/32 10.4.10 (amazon)
Linux/32 2.6 (chicago)
Linux/64 2.6 (chicago2)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix.
Description:
Test test_misc25b() open an existing test data file with RDWR unnecessarily.
(This was discovered during read-only test.)
Changed file open mode to RDONLY.
Tested platform:
Kagiso (readonly) only since it is a trivial change.
|
|
|
|
|
|
|
|
|
|
|
| |
Add some additional tests for reading non-contiguous selections from
datasets which haven't had any data written to them (both non-VL and VL
datatype fill values covered)
Tested on:
Mac OS X/32 10.4.9 (amazon)
FreeBSD/32 6.2 (duty)
FreeBSD/64 6.2 (liberty)
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed bugs w/VL-datatype fill values for chunked dataset storage.
Tested on:
Mac OS X/32 10.4.9 (amazon)
FreeBSD/32 6.2 (duty)
FreeBSD/64 6.2 (liberty)
Linux/32 2.6 (chicago)
Linux/64 2.6 (chicago2)
|
|
|
|
|
|
|
|
|
|
| |
Fix writing variable-length datatype fill values for contiguous dataset
storage
Tested on:
Mac OS X/32 10.4.9 (amazon)
Linux/32 2.6 (chicago)
Linux/64 2.6 (chicago2)
|
|
|
|
|
|
|
| |
It's output file from big.c. Unlink a temporary
file in big.c.
Tested on smirom because it's a simple change.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix compact dataset storage to initialize VL datatype fill values
correctly.
Also, fix bug in global heap code when the fix action on a global
heap is to delete an object in a heap with no free space.
Tested on:
Mac OS X/32 10.4.9 (amazon)
(Will be testing on FreeBSD/32 6.2 (duty))
|