gdal: Random test suite crash

Just ran into this on #510 (but can’t reproduce it easily):

Warning 1: GPKG: bad application_id=0x00000000 on '/tmp/.tmpgi6DfV.gpkg'
ERROR 1: Layer new already exists, CreateLayer failed.
Use the layer creation option OVERWRITE=YES to replace it.
test spatial_ref::srs::tests::predicats_epsg2154 ... ok
test spatial_ref::srs::tests::get_units_epsg4326 ... ok
test spatial_ref::srs::tests::non_existing_proj_param ... ok
test vector::layer::tests::test_create_layer_options ... ok
error: test failed, to rerun pass `--lib`

Caused by:
  process didn't exit successfully: `/home/grayshade/Projects/georust/gdal/target/debug/deps/gdal-0978520db0adc3dd` (signal: 11, SIGSEGV: invalid memory reference)

That looks like a temporary file name, not sure what’s going on.

About this issue

Original URL
State: open
Created 6 months ago
Comments: 23 (23 by maintainers)

Most upvoted comments

I don’t know if I can add something valuable to the dscussion, but we’ve recently added cargo as a dependency and our test suite ran with 0.76 but with 0.77 (https://github.com/geo-engine/geoengine/pull/929) one GdalOpenEx call with georust/gdal suddenly had a SIGSEGV.

Looking at this thread I noticed that 0.77 got a dependency of rusqlite, which again brought libsqlite3-sys=0.28. Removing this dependency seemed to remove the SIGSEGV… which is very scary.

ChristianBeilschmidt on Feb 11, 2024