-
Notifications
You must be signed in to change notification settings - Fork 96
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
Segmentation fault when DataSet::close is called #423
Comments
Yeah, sorry for that: #420. Please don't use it in the meanwhile. |
I think it exist so you can get notified of errors that occur while writing the data. It's pretty much not idiomatic to have close methods in Rust, and you can call |
See also https://github.com/rouault/gdal/blob/rfc91_text/doc/source/development/rfc/rfc91_dataset_close.rst. Flushing the cache isn't enough to make sure you're not going to silently lose errors. |
Okay, thank you. |
https://crates.io/crates/gdal/0.16.0 is now available. Sorry for the inconvenience. |
My program is stopping with a segmentation fault after calling close on a dataset.
Here's my test code:
The output:
I'm running this on Arch Linux. Here's the gdal version struct. Is 3.6.3 too new and do I need to downgrade?
I'm not getting my 'expect' message for closing, so I assume the seg fault is happening after that. My guess is that the functionality of close is being repeated by the dataset's implementation of Drop, and that's where the fault is happening.
If this is the case, why would I ever want to call 'close'?
The text was updated successfully, but these errors were encountered: