Opened 6 years ago

Last modified 5 years ago

#3715 new defect

v.out.ogr segfault with GPKG output

Reported by: vince Owned by: grass-dev@…
Priority: normal Milestone: 7.8.3
Component: Default Version: 7.4.2
Keywords: v.out.ogr Cc:
CPU: x86-64 Platform: MacOSX

Description

This happens while using GRASS in the QGIS toolbox. A r.contour operation runs fine, but when the result is about to be saved in a GPKG file, v.out.ogr crashes.

Backtrace:

1   libsqlite3.dylib         dbMallocRawFinish + 17
2   libsqlite3.dylib         sqlite3FindFunction + 886
3   libsqlite3.dylib         sqlite3CreateFunc + 499
4   libsqlite3.dylib         sqlite3_create_function_v2 + 488
5   libspatialite.7.dylib   register_spatialite_sql_functions + 68
6   libspatialite.7.dylib   spatialite_init_ex + 52
7   libgdal.20.dylib         OGRSQLiteBaseDataSource::InitNewSpatialite() + 302
8   libgdal.20.dylib         GDALGeoPackageDataset::InstallSQLFunctions() + 19
9   libgdal.20.dylib         GDALGeoPackageDataset::Create(char const*, int, int, int, GDALDataType, char**) + 485
10  libgdal.20.dylib         OGRGeoPackageDriverCreate(char const*, int, int, int, GDALDataType, char**) + 159
11  libgdal.20.dylib         GDALDriver::Create(char const*, int, int, int, GDALDataType, char**) + 1063
12  libgdal.20.dylib         OGR_Dr_CreateDataSource + 47
13  v.out.ogr                    main + 3564

I have upgraded to spatialite 5.0.0 beta0 in hope that would solve the problem, but no dice. Also, I run GDAL 2.3.2.

Saving as Shapefile works fine, though, so this is a mere inconvenience rather than a roadblock.

Change History (1)

comment:1 by neteler, 5 years ago

Milestone: 7.8.3
Note: See TracTickets for help on using tickets.