Bug#856472: gdal-bin: SrcDataSource ODBC Segmentation fault
Andy G Wood
agw at bas.ac.uk
Thu Mar 2 11:38:14 UTC 2017
Hi Bas,
> Can you install the gdal-bin-dbgsym & libgdal20-dbgsym packages an run
> the ogrinfo command via gdb to get a backtrace?
There does not appear to be an amd64 architecture version of these packages,
so I am a bit stuck with this?
> Can you also provide a minimal test case to reproduce the issue on a
> system which doesn't have your ODBC data source configured?
The system which exhibits the problem is using an Oracle 11g ODBC driver
(testing this outside of gdal shows no problems). The following builds a test
case with sqlite, but unfortunately this works fine!
1. install package libsqliteodbc
2. create test sqlite database:
sqlite3 -batch database.sqlite < create_db.sql
The contents of create_db.sql are:
CREATE TABLE table1(lat,lon);
INSERT INTO table1(lat,lon) VALUES(-54.00827,-38.06391),(-54.01001,-38.06845);
3. add this to ~/.odbc.ini :
[mysqlitedb]
Description=My SQLite test database
Driver=SQLite3
Database=/<full path>/database.sqlite
4. check with ogrinfo:
ogrinfo -ro -al gdaltest.xml
The contents of gdaltest.xml are:
<OGRVRTDataSource>
<OGRVRTLayer name="test">
<SrcDataSource>ODBC:mysqlitedb</SrcDataSource>
<SrcSQL>
select lon, lat from table1
</SrcSQL>
<GeometryType>wkbPoint</GeometryType>
<LayerSRS>WGS84</LayerSRS>
<GeometryField encoding="PointFromColumns" x="LON" y="LAT"/>
</OGRVRTLayer>
</OGRVRTDataSource>
The final bit of information I have for now is that the last time this worked
fine from packages in Testing is Mar 2 2016. I have not run my system between
then and yesterday (Mar 1 2017).
Andy.
More information about the Pkg-grass-devel
mailing list