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.

Sign up for GitHub

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

Jump to bottom

Handle cases where errors cannot be retrieved using CPLGetLastErrorNo() #21

Open

jrgriffiniii opened this issue Jun 26, 2019 · 1 comment

jrgriffiniii commented Jun 26, 2019

This is normally used to find error codes when SQL executions fail (please see https://gdal.org/python/osgeo.ogr-pysrc.html#DataSource.ExecuteSQL)

jrgriffiniii mentioned this issue

New version of the build system, fixed an error I was having. #20

Merged

Author

jrgriffiniii commented Jun 26, 2019

This should return an error code until some memory issues are encountered in https://github.com/OSGeo/gdal/blob/master/gdal/port/cpl_error.cpp#L152 when invoking https://github.com/OSGeo/gdal/blob/master/gdal/port/cpl_error.cpp#L821. I'm not certain that https://github.com/OSGeo/gdal/blob/master/gdal/port/cpl_multiproc.cpp#L2320 is doing more than just checking for memory allocation errors from https://github.com/OSGeo/gdal/blob/master/gdal/port/cpl_error.cpp#L149

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment