We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The HDF4 test tst_h4_lendian fails valgrind like this:
==6719== ==6719== HEAP SUMMARY: ==6719== in use at exit: 544 bytes in 31 blocks ==6719== total heap usage: 8,950 allocs, 8,919 frees, 10,631,683 bytes allocated ==6719== ==6719== LEAK SUMMARY: ==6719== definitely lost: 0 bytes in 0 blocks ==6719== indirectly lost: 0 bytes in 0 blocks ==6719== possibly lost: 0 bytes in 0 blocks ==6719== still reachable: 544 bytes in 31 blocks ==6719== suppressed: 0 bytes in 0 blocks
The text was updated successfully, but these errors were encountered:
OK, I have a fix for this working in HPC netCDF. When some PRs get merged I will put up a PR for this issue.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
The HDF4 test tst_h4_lendian fails valgrind like this:
The text was updated successfully, but these errors were encountered: