[gdal-dev] ogr2ogr segfault

[a.furieri at lqt.it]

On Tue, 19 May 2015 11:25:27 +0200, Even Rouault wrote:
> Debian Sid, might be a platform specific issue?
> https://bugs.debian.org/785091
>

few technical details useful to understand better:

a) starting since November 2013 it become definitely clear
    that the older self-registration mechanism based on the
    spatialite_init() API was intrinsically thread unsafe
    and could potentially have very bad interactions with
    the more recent versions of both PROJ.4 and GEOS

b) consequently a public announcement [1] was duly released
    warning about the deprecation of spatialite_init()
    and soliciting developers and maintainers to start
    supporting the alternative thread safe mechanism based
    on spatialite_alloc_connection(), spatialite_init_ex()
    and spatialite_cleanup() APIs.

c) all recent versions of libspatialite, spatialite-tools
    and spatialite_gui are now expected to be fully thread
    safe: and AFAIK the same is for recent versions of GDAL.
    any obsolete version still based on the nowadays deprecated
    spatialite_init() API is potentially at risk when deployed
    in a multithread configuration.

OTH Sandro

[1] 
https://groups.google.com/forum/#!searchin/spatialite-users/spatialite_init_ex/spatialite-users/83SOajOJ2JU/sgi5fuYAVVkJ