On 2015-07-16 12:16, Moritz Lennert wrote:
On 14/07/15 22:04, Sebastiaan Couwenberg wrote:
On 07/14/2015 09:22 PM, Moritz Lennert wrote:
Anything else I can do to debug, or is this the spatialite bug and I
just have to wait for a new version to get into testing ?
Please try to above so we can find out if the deprecated
spatialite_init() method is causing the segfault.
That seems to be the case:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff0141ff4 in spatialite_init ()
from /usr/lib/x86_64-linux-gnu/libspatialite.so.5
Thanks for the confirmation.
Today the spatialite transition started so we'll soon have SpatiaLite
4.3.0 in testing, this is part of the solution to the
spatialite_init()
related problems. Another part is the upcoming transition to GDAL
1.11,
and for QGIS we'll need the next LTR (2.8.3). QGIS 2.8.2 doesn't have
the spatialite_init() related fixes yet.
Ok, that means that there's not much I can do expect install QGIS
master ?
The upstream QGIS nightly packages are an option if you can't wait for
the 2.8.3 release.
As mentioned in my previous message to this bugreport [1], I'll include
the spatialite changes from QGIS 2.8.3 as patch in the QGIS 2.8.2
package in Debian if the 2.8.3 release takes too long.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791680#32
Kind Regards,
Bas
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
