-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
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
nc_open "Abort" crash on a corrupted netCDF classic file #2731
Comments
re: Issue Unidata#2731 A corrupted classic file is causing the library to crash. Fix so that it returns NC_ENOTNC instead.
Fixed by PR #2732 |
Wow, thank you so much for a speedy response and fix, Dennis and Ward! |
Thanks again for the super-quick action on this! Wanted to check, is there an approximate timeline for the new netCDF release? Trying to evaluate if we should patch this in our netCDF version now or wait till we can upgrade to the new release that will include this fix. |
No worries and all credit for the fix to @DennisHeimbigner! I don't have a timeline, we are working through some other issues. I'd like to think we will resolve them very quickly but I'd be over-promising. Patching in for now is probably the safest bet :). |
Hello netCDF folks!
We are seeing the following crash on a corrupted netcdf file (see nctest_classic_corrupted.nc attached in a ZIP file, nctest_classic_corrupted.nc.zip):
This is on a mac machine, but we see this crash on all platforms.
Here is the code to reproduce the issue:
I understand that it makes sense that netCDF functionality does not work on a corrupted file, but it would be nice if a crash could be avoided (even when the file is bad).
We are using netCDF-C v4.9.1.
Thanks in advance for taking a look!
Kris
The text was updated successfully, but these errors were encountered: