summaryrefslogtreecommitdiffstats
path: root/config
diff options
context:
space:
mode:
authorRobb Matzke <matzke@llnl.gov>1999-04-27 14:47:54 (GMT)
committerRobb Matzke <matzke@llnl.gov>1999-04-27 14:47:54 (GMT)
commit2dc738a321e45ce1e0c5edcc2bf7f3623e823c9e (patch)
treebd07d5bdb789fed39d8a77122ed0d5613c1cb0b9 /config
parenta66c628b3c5e06e5ab188400d18c7565e5a0d738 (diff)
downloadhdf5-2dc738a321e45ce1e0c5edcc2bf7f3623e823c9e.zip
hdf5-2dc738a321e45ce1e0c5edcc2bf7f3623e823c9e.tar.gz
hdf5-2dc738a321e45ce1e0c5edcc2bf7f3623e823c9e.tar.bz2
[svn-r1224] Changes since 19990426
---------------------- ./tools/h5tools.c ./tools/h5tools.h Finally fixed a long-standing bug that caused core dumps if a compound datum rendered to more than some number of characters (we kept bumping up the limit at the risk of violating stack size limits on some machines). The fix works only on systems that have the vsnprintf() function (otherwise a 4kB limit is imposed, which if violated probably dumps core). If vsnprintf() is present then the library dynamically allocates space for the output string. Also made it possible to control how compound data is rendered across multiple lines of output by allowing the caller to specify where optional line-breaks get inserted. The output functions split up the value at one or more optional line-breaks to prevent it from wrapping around the screen. If a datum doesn't fit on the current line but would fit on the next line then it is printed on the next line regardless of whether optional line-breaks would have prevent wrapping around the screen. This makes it easier to find the beginnings of compound data values. This feature is disabled by default but can be enabled by the application. If a datum doesn't fit on the current line and the previous datum also occupied more than one line then we move to the next line before printing. This makes it easier to find the beginnings of compound data values but prevents the output from looking fragmented if there are only a few long values among mostly short values. This feature is disabled by default but can be enabled by the application. The application can control the printf() formats used for all the native data types. The defaults are what the library used to use: %g, %ld, %lu, %d, and %u ./tools/h5ls.c Compound datatype values can now be split across multiple lines of output instead of just wrapping. Also, when lots of compound values are too long they all start at the beginning of a line. This only required about 10 lines of changes in the setup for tools library calls (I didn't modify the h5dump program because it uses its own version of the tools library that forked off long ago). Added code for Win32 which is unable to cast `unsigned long long' to `double'. If the dataset size exceeds (2^63)-1 then the percent utilization is not displayed (this is easily possible with chunked datasets). This is untested yet. ./configure.in ./src/H5config.h.in ./src/H5.c ./src/H5private.h Check for vsnprintf() and provide a simple, stupid definition if it isn't available. The stupid definition just calls vsprintf() and ignores the second argument. This can result in buffer overflows in h5ls and h5dump since vsprintf() is an unsafe function (and anyone can create an hdf5 file that runs an arbitrary command from h5ls and h5dump in that case)! ./config/conclude.in Remove more *.o files for `make clean' ./src/H5A.c ./src/H5D.c ./src/H5F.c ./src/H5I.c ./src/H5Iprivate.h ./src/H5P.c ./src/H5R.c ./src/H5RA.c ./src/H5S.c ./src/H5T.c ./src/H5TB.c Cleaned up a memory leak during H5_term_library() by allowing H5I_clear_group() to skip items that couldn't be freed. This allows the item to remain in the group until we can free it later. ./src/H5F.c The H5F_close_all() function fails if a file cannot be closed.
Diffstat (limited to 'config')
-rw-r--r--config/conclude.in3
1 files changed, 2 insertions, 1 deletions
diff --git a/config/conclude.in b/config/conclude.in
index 51cf691..63bd512 100644
--- a/config/conclude.in
+++ b/config/conclude.in
@@ -98,7 +98,8 @@ uninstall:
#
mostlyclean:
-$(RM) $(LIB_OBJ) $(LIB_OBJ:.lo=.o)
- -$(RM) $(TEST_OBJ) $(PROG_OBJ) $(MOSTLYCLEAN)
+ -$(RM) $(TEST_OBJ) $(TEST_OBJ:.lo=.o)
+ -$(RM) $(PROG_OBJ) $(PROG_OBJ:.lo=.o) $(MOSTLYCLEAN)
# Like `mostlyclean' except it also removes the final targets: things like
# libraries and executables. This target doesn't remove any file that