summaryrefslogtreecommitdiffstats
path: root/tools/h5repack
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r17645] Purpose:Mike McGreevy2009-10-152-9/+16
| | | | | | | | | | | | | | | Merge from Trunk Description: Merging all of my CFLAGS-related changes from trunk to 1.8 This includes revision #s: 17616, 17625, 17627, 17639, and 17643. Tested: h5committest and some additional checks on our FreeBSD as well as NCSA's machines.
* [svn-r17607] ode Cleanup:Albert Cheng2009-10-071-41/+16
| | | | | | | | TFLOPS machine has retired long ago. Removed all code specific for its support. Test: h5committested.
* [svn-r17555] Description:Quincey Koziol2009-09-293-45/+44
| | | | | | | | | | | | | | | | | | | | | | | | Bring r17553 from trunk to 1.8 branch: Bring general fixes/improvements from file_free_space branch back to trunk. Tested on: FreeBSD/32 6.3 (duty) in debug mode FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (jam) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-amd64 2.6 (smirom) w/Intel compilers w/default API=1.6.x, w/C++ & FORTRAN, in production mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode Mac OS X/32 10.5.8 (amazon) in debug mode Mac OS X/32 10.5.8 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r17441] Purpose:Mike McGreevy2009-08-312-1/+10
| | | | | | | | | | | | | | | | | | | | | Merge from trunk Description: Merged revisions 17228 and 17440 from trunk to 1.8 Specifically, this brings support of --enable-static-exec flag into 1.8 Tested: Manually on jam, linew, smirom, liberty, plus h5committest. Currently, there is no automatic regression test that exists due to portability issues. Behavior is both different and undefined on certain systems (and while 'nm' command seems to exist on all machines, behavior is confirmed to be different on Mac, possibly others). Solution will be to set up some sort of framework in daily tests to build statically, remove shared paths, and verify executables can function.
* [svn-r17439] Purpose:Mike McGreevy2009-08-311-54/+104
| | | | | | | | | | | | | | | | | | | | | | Updating autotools Description: Bring revisions 17345 and 17357 from trunk to 1.8, specifically: - Automake upgraded to 1.11 - Autoconf upgraded to 2.64 - bin/reconfigure script edited to use new versions (on jam), and run to generate new configure script and Makefile.in's. - configure.in script edited to add "_cv_" to all AC_CACHE_VAL strings (in order to comply with new autoconf standard). - bin/install-sh script replaced with new version as provided by automake. Tested: - All issues on trunk were resolved, so only tested on jam and linew. Any other outliers should be caught by daily tests.
* [svn-r17314] Description:Quincey Koziol2009-08-103-12/+4
| | | | | | | | | | | | | | | | | | | | | | Bring r17313 from trunk to 1.8 branch: Bring back various minor code cleanups from the file free space branch Tested on: FreeBSD/32 6.3 (duty) in debug mode FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-amd64 2.6 (smirom) w/Intel compilers w/default API=1.6.x, w/C++ & FORTRAN, in production mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode Mac OS X/32 10.5.8 (amazon) in debug mode Mac OS X/32 10.5.8 (amazon) w/C++ & FORTRAN, w/threadsafe, in production mode
* [svn-r17266] Description:Quincey Koziol2009-07-301-1/+1
| | | | | | | | | Clean up various compiler warnings from IRIX64 build Tested on: Mac OS X/32 (amazon) debug & production (yes, I know it's not an IRIX64 system :-) Too minor to require h5committest
* [svn-r17077] merge 17076 from trunkPedro Vicente Nunes2009-06-173-67/+88
| | | | | | | bug fix: h5repack was not applying a requested contiguous layout for a dataset with filters added a test to the C program test (not to the script), that verifies the layout and filters tested: linux
* [svn-r17053] merge 17052 from trunkPedro Vicente Nunes2009-06-151-0/+38
| | | | | | | | | | Add a run to the h5repack shell script to read a family file The file used for input is located in the common source tools for testfiles, in tools/testfiles Modified the h5repack shell script to read files from this location (h5repack reads its input files from a dedicated testfiles location in h5repack/testfiles) Changed the h5diff open file call to use h5tools_fopen, so that it can open all file drivers Tested: linux
* [svn-r16843] Description:Mike McGreevy2009-04-222-0/+6
| | | | | | | | | | | | Adding dependency to h5repack test script. h5repack.sh needs h5repacktst to run first. Tested: Problem only appeared on Glory, but tested the dependence manually on jam by trying to run only the script and checking that it first ran the h5repacktst test program.
* [svn-r16802] Purpose: Fix bug 1516Neil Fortner2009-04-204-21/+384
| | | | | | | | | | | Description: h5repack previously would not take named datatypes into consideration when copying datasets and attributes. This would cause extra anonymous datatypes in the target file at best, and cause errors halfway through the repacking at worst. h5repack should now always handle named datatypes correctly. Named datatypes are also now converted to the native type when -n is given. Tested: jam, linew, smirom (h5committest)
* [svn-r16793] Description:Mike McGreevy2009-04-201-4/+4
| | | | | | | | | | | | - Updated bin/reconfigure to use latest version of automake (1.10.2). Regenerated Makefile.in's by running bin/reconfigure. - Added libtool version numbers to c++, fortran, hl, hl c++, and hl fortran libraries. Tested: jam, liberty, smirom
* [svn-r16672] merge 16671 from trunkPedro Vicente Nunes2009-04-061-1/+1
| | | | fix compiler error on a missing "static" declaration
* [svn-r16664] merge 16663 from trunkPedro Vicente Nunes2009-04-035-212/+274
| | | | | | | | note : lots of weird warnings of the type ../../../../hdf5/tools/h5repack/h5repacktst.c:3919: warning: will never be executed appear on the same code as 1.9 for the 1.8 branch tested: linux
* [svn-r16658] merge from trunk 16656Pedro Vicente Nunes2009-04-024-2124/+2540
| | | | | | | | #1402 (B1) h5repack does not preserve creation order indexing. ISSUE : h5repack does not handle group creation order flags. ACTION: call H5P(g)(s)et_link_creation_order functions when handling groups, add new groups with these flags to the test generation program, and verify results in the test program. TEST: in the test program, function that compares property lists, added code to verify groups DOCS: Added the note to RELEASE.txt: "h5repack now handles group creation order. PVN - 2009/4/2 - 1402".
* [svn-r16641] merge from trunk revs 16614, 16629Pedro Vicente Nunes2009-04-015-5/+57
| | | | | | | | | | | 1. #1501 (B1) tools bug if dataset is larger than H5TOOLS_BUFSIZE limit. ISSUE : the tools use the following formula to read by hyperslabs: hyperslab_size[i] = MIN( dim_size[i], H5TOOLS_BUFSIZE / datum_size) where H5TOOLS_BUFSIZE is a constant defined of 1024K. This is OK as long as the datum_size does not exceed 1024K, otherwise we have a hyperslab size of 0 (since 1024K/(greater than 1024K) = 0). This affects h5dump. h5repack, h5diff SOLUTION: add a check for a 0 size and define as 1 if so. TEST FOR H5DUMP: Defined a case in the h5dump test generator program of such a type (an array type of doubles with a large array dimension, that was the case the user reported). Since the written file commited in svn would be around 1024K, opted for not writing the data (the part of the code where the hyperslab is defined is executed, since h5dump always reads the files). Defined a macro WRITE_ARRAY to enable such writing if needed. Added a run on the h5dump shell script. Added 2 new files to svn: tools/testfiles/tarray8.ddl, tools/testfiles/tarray8.h5. NOTE: while doing this I thought of adding this dataset case to an existing file, but that would add the large array output to those files (the ddls). The issue is that the file list is increasing. TEST FOR H5DIFF: for h5diff the check for reading by hyperslabs is H5TOOLS_MALLOCSIZE (128 * H5TOOLS_BUFSIZE) or 128 Mb. This makes it not possible to add such a file to svn, so used the same method as h5dump (only write the dataset if WRITE_ARRAY is defined). As opposed to h5dump, the hyperslab code is NOT executed when the dataset is empty (dataset is not read). Added the new dataset to existing files and shell run (tools/h5diff/testfiles/h5diff_dset1.h5 and tools/h5diff/testfiles/h5diff_dset2.h5 and output in tools/h5diff/testfiles/h5diff_80.txt). TEST FOR H5REPACK: similar issue as h5diff with the difference that the hyperslab code is run. Added a run to the shell script (with a filter, otherwise the code uses H5Ocopy). FURTHER ISSUES: the type in question ("double") has a different output cross platforms (e.g on liberty some garbage number is printed at some array locations) SOLUTION: defined an "int" type for this test. However the printing of such an array has a bogus output at least in one platform (FreeBsd), so eliminated the test run altogether and filed a bug report on this
* [svn-r16566] Description:Quincey Koziol2009-03-111-0/+8
| | | | | | | | Bring r16560 back from trunk. Tested on: Mac OS X/32 10.5.6 (amazon) debug & production (Following up with tests on more platforms)
* [svn-r16562] Purpose:Mike McGreevy2009-03-101-3/+3
| | | | | | | | | | | | | | | | | | Bug Fix Description: Fixing BZ #1381. The --includedir=DIR configure option, which is used to spceify installation location of C header files, did not work correctly as the path was hard-coded into config/commence.am. I'm presuming this is because an older version of automake didn't know where to put C header files. In any case, removing this line now defaults the includedir to the same directory that it is currently hard-coded to, and also fixes the configure flag which allows for customization of this value. Tested: jam, liberty
* [svn-r16519] merge 16518 from trunkPedro Vicente Nunes2009-02-261-0/+1
| | | | | | have 2 expected outputs for 2 h5ls runs depending if run on a big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output) the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other tested: jam, linew
* [svn-r16490] Fixed bug #1459 by eliminating the macro long_long and ↵Allen Byrne2009-02-181-1/+1
| | | | | | | | | replacing all instances with long long. Tested: h5comittest fedora 10 x64 XP32, VNET
* [svn-r16402] Description:Quincey Koziol2009-02-032-0/+5
| | | | | | | | | | | Bring r16401 back from trunk: Correct error introduced in r16353 with layout version, and add test so it gets caught earlier. Tested on: FreeBSD/32 6.3 (duty) Too minor to require h5committest
* [svn-r16313] merge 16301Pedro Vicente Nunes2009-01-141-1/+1
| | | | | | | | | | | | | Add a mention to the usage that the default minimum size for compression is 1024 bytes M - is an integer greater than 1, size of dataset in bytes (default is 1024) #bgz 1426 tested: windows, linux
* [svn-r16115] #1375. Define a default chunk whose size is manageable. Defined ↵Pedro Vicente Nunes2008-11-213-14/+43
| | | | | | currently as the same size of hyperslab (that compares the dimension sizes against a predefined constant size and chooses the minimum between the two) Tested : linux, windows
* [svn-r15985] reorganized the code to deal with deprecated -i -o for in/out ↵Pedro Vicente Nunes2008-10-291-186/+45
| | | | | | | | files to avoid duplicated code tested: windows, linu x
* [svn-r15898] Purpose: Bug FixMike McGreevy2008-10-171-6/+1
| | | | | | | | | | | | | | | Description: Libtool wasn't working on linew because the script was not working with the Solaris Bourne shell. Libtool has built- in detection to ensure that it uses an appropriate shell, but our config/commence.am was hard coding this shell to be /bin/sh. Removing this line allows the shell to be picked up by configure, thus allowing libtool to use the correct shell on linew (bash). This was initially added to correct for a problem on an old machine (janus), so shoudn't be needed for machines we currently support. Tested: full make check install on kagiso and linew, compile only on smirom, duty, and liberty.
* [svn-r15881] Purpose: Bug Fixes, Libtool UpgradeMike McGreevy2008-10-151-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Description: 1) configure now sets LD_LIBRARY_PATH before checking for presence of SZIP encoder, so user does not need to set this. The path is then saved and sent to Makefiles, and used when "make check-install" is invoked, so user doesn't need to set this manually. 2) Upgraded libtool to version 2.2.6a 3) Rearranged tools build order as h5dump depends on existence of h5diff and h5import. Since h5dump is a sister directory as opposed to a parent of either, it doesn't know about the build rules of these tools, so setting any sort of explicit dependency confuses automake as it won't know how to build the tools. Instead, setting CONFIG = ordered forces an in-order traversal of each tools subdirectory. (without it will also traverse in order by default, but this should prevent gmake's -j option from jumping ahead as well). 'make check install' should now be able to be invoked after 'configure' without causing a dependency failure. 4) Removed H5_HAVE_LARGE_HSIZET macro from vms/src/h5pubconf.h, as this macro has now been out of the code for some time. (vms pubconf needs to be updated manually, which is why it was still hanging around). Tested: kagiso, smirom, liberty Note: h5diff looks to be causing failures in h5copy and h5dump tools tests, though these were present before any of my changes. My changes only affect build order and configuration setup, and shouldn't prevent fixes for these failures coming in after this checkin. Other than these, tests pass fine.
* [svn-r15871] Eliminate -c option and make that behavior the default and ↵Pedro Vicente Nunes2008-10-152-5/+2
| | | | | | return 2 instead of -1 on error status Tested: windows, linux
* [svn-r15791] Bug fix. When detecting the user requested filters, the "all" ↵Pedro Vicente Nunes2008-10-061-1/+5
| | | | | | option was not taken in consideration when printing the compression ratio Tested: windows, linux
* [svn-r15750] move h5repack test files to /tools/h5repack/testfilesPedro Vicente Nunes2008-10-0118-6/+8
| | | | tested: linux
* [svn-r15680] Pedro Vicente Nunes2008-09-223-42/+74
| | | | | Formatted code Tested: windows, linux
* [svn-r15663] fix commentsPedro Vicente Nunes2008-09-191-8/+15
| | | | tested: linux
* [svn-r15662] Cleaned compiler warnings Pedro Vicente Nunes2008-09-198-299/+285
| | | | | | | | Bug fixes: change the options block size variable from int to hsize_t, to match the H5Pset_userblock call, do not print print compression ratio when the requested filter is NONE Tested: windows, linux
* [svn-r15646] Cleaned compiler warnings Pedro Vicente Nunes2008-09-171-4/+4
| | | | | | Bug fix: change the options block size variable from int to hsize_t, to match the H5Pset_userblock call Tested: windows, linux
* [svn-r15642] Pedro Vicente Nunes2008-09-175-3805/+3889
| | | | | | | | Add a default user block size of 1024 when none is given add a failure condition of writing user block Tested: windows, linux
* [svn-r15629] Description:Quincey Koziol2008-09-1610-574/+574
| | | | | | | | | | | | | Remove trailing whitespace from C/C++ source files, with the following script: foreach f (*.[ch] *.cpp) sed 's/[[:blank:]]*$//' $f > sed.out && mv sed.out $f end Tested on: Mac OS X/32 10.5.5 (amazon) No need for h5committest, just whitespace changes...
* [svn-r15558] 1) There are 2 new command line parameters for h5repack. ↵Pedro Vicente Nunes2008-08-297-27/+188
| | | | | | | | | | | | | | Together they allow a call to H5Pset_alignment to be made -t T, --threshold=T Threshold value for H5Pset_alignment -a A, --alignment=A Alignment value for H5Pset_alignment 2) bug fix the printing of the dataset name was not done for references (verbose mode) tested: windows, linux
* [svn-r15533] #1184Pedro Vicente Nunes2008-08-266-33/+323
| | | | | | | | | | | Add a userblock to an HDF5 file during the repack. The user gives give a filename and userblock size as command line parameters to h5repack and the contents of that file are stored in the userblock for the HDF5 file created by h5repack. New flags to handle this -u and -b Tested : windows, linux
* [svn-r15463] Description:Quincey Koziol2008-08-121-0/+1
| | | | | | | | Bring revision 15462 (compiler warnings) back from trunk. Tested on: Mac OS X/32 10.5.4 (amazon) w/FORTRAN & C++ (Too minor to require h5committest)
* [svn-r15436] bug fixPedro Vicente Nunes2008-08-061-11/+11
| | | | | | | the compression ratio was being printed for cases where a layout was requested and not a filter tested: windows, linux
* [svn-r15433] http://bugzilla.hdfgroup.uiuc.edu/show_bug.cgi?id=1170Pedro Vicente Nunes2008-08-052-2/+5
| | | | | | | | | | | | | Summary: when using h5diff to compare the results of h5repack (or other tools that copy one HDF5 file to another), a new option is needed to allow h5diff to make an "absolute" comparison of the 2 files. This is the "contents" mode explained in the usage below. If this mode is present, objects in both files must match (must be exactly the same). If this does not happen, the tool returns an error code of 1 (instead of the success code of 0) Changes to the h5repack test script: the call to h5diff was changed to include -c (maintaining the previous -q). tested: windows, linux
* [svn-r15053] Add a test for the 1.6.7 -i infile -o outifle for backward ↵Pedro Vicente Nunes2008-05-211-0/+37
| | | | | | | | compability Used the function TOOLTEST from 1.6.7 Tested: linux
* [svn-r15048] bug fix regarding change from -i to -d regarding number of ↵Pedro Vicente Nunes2008-05-201-1/+1
| | | | | | links in indexed format tested: windows
* [svn-r15042] Bug fix.Albert Cheng2008-05-201-4/+4
| | | | | | | | | | | | | | | | | | | Description: The fortran Makefile.am used HDF_FORTRAN to indicate it is part of the Fortran API source so that conclude.am will give fortran api prefix in the test output. The symbox HDF_FORTRAN is also used in configure for a different purpose (indicated --enable-fortran). They conflicted. Similar problem for the symbol HDF_CXX. Solution: Changed all the involved Makefile.am to use "FORTRAN_API" instead. It is a more appropriate name. Same for CXX_API. Along the way, discovered that the Makefile.am of hl/fortran/test and hl/cxx/test did not have those symbols at all. Added them in. Platform tested: Kagiso serial and h5committested (kagisopp, smirom, linew).
* [svn-r15033] Purpose:Albert Cheng2008-05-191-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improvement. Description: src/libhdf5.settings was the initial configure summary and is installed. Then configure is changed to dump a summary of the configure settings to the output and also append it to src/libhdf5.settings. That created two different output formats and duplicated information. This is the initial attempt to clean up this confusion and unify the output format. It is decided to use the src/libhdf5.settings template as the unified means. This requires more macros symbols be defined. The following symbols are all related to generating the src/libhdf5.settings file. AC_SUBST(EXTERNAL_FILTERS) AC_SUBST(MPE) MPE=no AC_SUBST(STATIC_EXEC) STATIC_EXEC=no AC_SUBST(HDF_FORTRAN) HDF_FORTRAN=no AC_SUBST(FC) HDF_FORTRAN=no AC_SUBST(HDF_CXX) HDF_CXX=no AC_SUBST(CXX) HDF_CXX=no AC_SUBST(HDF5_HL) HDF5_HL=yes AC_SUBST(GPFS) GPFS=no AC_SUBST(LINUX_LFS) LINUX_LFS=no AC_SUBST(INSTRUMENT) INSTRUMENT=no AC_SUBST(CODESTACK) CODESTACK=no AC_SUBST(HAVE_DMALLOC) HAVE_DMALLOC=no AC_SUBST(DIRECT_VFD) DIRECT_VFD=no AC_SUBST(THREADSAFE) THREADSAFE=no AC_SUBST(STATIC_SHARED) AC_SUBST(enable_shared) AC_SUBST(enable_static) AC_SUBST(UNAME_INFO) UNAME_INFO=`uname -a` The src/libhdf5.settings.in has CONDITIONAL's added to it too. The untrue conditions turned into a "#" and these lines are cleaned by the post processing script. Platform tested: h5committest on kagiso, smirom and linew. (smirom had failures not due to my changes.)
* [svn-r15024] backward compatibility for old -i infile -o outfile optionsPedro Vicente Nunes2008-05-162-18/+195
| | | | | | | | | | | | | if these are detected this syntax is used, otherwise the one in usage is used there was another -i option for -i L2, --indexed=L2 Minimum number of links in the indexed format That was changed to -d -d L2, --indexed=L2 Minimum number of links in the indexed format Tested: windows, linux
* [svn-r15006] Purpose: configure cleanupMike McGreevy2008-05-151-1/+0
| | | | | | | Description: cleaning up configure related to removal of --disable-hsizet flag, which we no longer support. Tested: kagiso
* [svn-r14915] Pedro Vicente Nunes2008-05-011-11/+15
| | | | | | | Introduced a compression ratio = uncompressed size / compressed size in the printing of the compression with 3 digits of precision per hdf-forum NASA developers suggestion tested: windows, linux
* [svn-r14824] Purpose: Updating HDF5 1.8 to use automake 1.10.1 and ↵Mike McGreevy2008-04-101-16/+20
| | | | | | | | | | | | | | | | | | libtool 2.2 Description: Updated bin/reconfigure script to reflect the new versions of libtool and automake in the /home1/packages/ directory. Rearranged configure.in script. For some reason, when using libtool 2.2, the libtool script doesn't generate until later in the configuration process, so I had to move a test that parsed through the libtool script to a point after where it was actually being generated. Ran libtoolize on the project, and ran bin/reconfigure to regenerate configure and Makefile.in's throughout. Tested: kagiso, smirom, linew, tg-login
* [svn-r14413] Description:Quincey Koziol2008-01-141-1/+1
| | | | | | | | | | | | | | | | | | | Change H5P[gs]et_format_bounds() => H5P[gs]et_libver_bounds() and also enumerated values H5F_FORMAT_{EARLIEST, LATEST} => H5F_LIBVER_{EARLIEST, LATEST} Tested on: FreeBSD/32 6.2 (duty) in debug mode FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, in production mode Mac OS X/32 10.4.10 (amazon) in debug mode Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
* [svn-r14402] Description:Quincey Koziol2008-01-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: FreeBSD/32 6.2 (duty) in debug mode FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, in production mode Mac OS X/32 10.4.10 (amazon) in debug mode Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
generated by cgit v0.12 at 2025-02-19 20:15:21 (GMT)