mirror of
https://github.com/Unidata/netcdf-c.git
synced 2024-11-27 07:30:33 +08:00
d07c05b58f
re: issue https://github.com/Unidata/netcdf-c/issues/1156 Starting with HDF5 version 1.10.x, the plugin code MUST be careful when using the standard *malloc()*, *realloc()*, and *free()* function. In the event that the code is allocating, reallocating, or free'ing memory that either came from -- or will be exported to -- the calling HDF5 library, then one MUST use the corresponding HDF5 functions *H5allocate_memory()*, *H5resize_memory()*, *H5free_memory()* [5] to avoid memory failures. Additionally, if your filter code leaks memory, then the HDF5 library generates a failure something like this. ```` H5MM.c:232: H5MM_final_sanity_check: Assertion `0 == H5MM_curr_alloc_bytes_s' failed. ```` This PR modifies the code in the plugins directory to conform to these new requirements. This raises a question about the libhdf5 code where this same problem may occur. We need to scan especially nc4hdf.c to look for this problem. |
||
---|---|---|
.. | ||
images | ||
obsolete | ||
old | ||
static-pages | ||
.gitignore | ||
all-error-codes.md | ||
architecture.dox | ||
attribute_conventions.md | ||
auth.html | ||
auth.md | ||
bestpractices.md | ||
building-with-cmake.md | ||
cdl.dox | ||
CMakeLists.txt | ||
COPYRIGHT.dox | ||
credits.md | ||
DAP2.dox | ||
DAP4.dox | ||
dispatch.dox | ||
docmap.pdf | ||
Doxyfile.developer | ||
Doxyfile.in | ||
DoxygenLayout.xml | ||
esg.md | ||
FAQ.md | ||
file_format_specifications.md | ||
filters.md | ||
footer.html | ||
groups.dox | ||
guide.dox | ||
header.html | ||
indexing.dox | ||
inmeminternal.dox | ||
inmemory.md | ||
install-fortran.md | ||
install.md | ||
internal.dox | ||
known_problems.md | ||
mainpage.dox | ||
Makefile.am | ||
netcdf-50x50.png | ||
netcdf.m4 | ||
notes.md | ||
OPeNDAP.dox | ||
release_header.html | ||
release.css | ||
tests.md | ||
testserver.dox | ||
tutorial.dox | ||
types.dox | ||
unidata_logo_cmyk.png | ||
user_defined_formats.md | ||
windows-binaries.md |