Hello,I have compiled Spatialite 4.4.0-RC1 for iOS and encounter a crash (SIGABRT) when I call spatialite_cleanup_ex. It appears to be due to cache->gaia_rttopo_error_msg being freed in free_internal_cache in alloc_cache.c without having been allocated previously.Any idea how I can fix this?
On Wednesday, 27 July 2016 16:39:24 UTC+2, Aaron Farnham wrote:Hello,I have compiled Spatialite 4.4.0-RC1 for iOS and encounter a crash (SIGABRT) when I call spatialite_cleanup_ex. It appears to be due to cache->gaia_rttopo_error_msg being freed in free_internal_cache in alloc_cache.c without having been allocated previously.Any idea how I can fix this?On the fly, no.When the structure it belongs too is being initialized, the pointer is set to NULL- after every every free, it is also set to NULL- free is done only after checking for NULL
On Wednesday, 27 July 2016 17:17:55 UTC+2, mj10777 wrote:
On Wednesday, 27 July 2016 16:39:24 UTC+2, Aaron Farnham wrote:Hello,I have compiled Spatialite 4.4.0-RC1 for iOS and encounter a crash (SIGABRT) when I call spatialite_cleanup_ex. It appears to be due to cache->gaia_rttopo_error_msg being freed in free_internal_cache in alloc_cache.c without having been allocated previously.Any idea how I can fix this?On the fly, no.When the structure it belongs too is being initialized, the pointer is set to NULL- after every every free, it is also set to NULL- free is done only after checking for NULLJust checked the RC1 version of the source, no changes were made in this area- everywhere where cache->gaia_rttopo_error_msg is dealt with, seems to be properly checked for (or set to) NULL
On Wednesday, July 27, 2016 at 10:32:05 AM UTC-5, mj10777 wrote:
On Wednesday, 27 July 2016 17:17:55 UTC+2, mj10777 wrote:
On Wednesday, 27 July 2016 16:39:24 UTC+2, Aaron Farnham wrote:Hello,I have compiled Spatialite 4.4.0-RC1 for iOS and encounter a crash (SIGABRT) when I call spatialite_cleanup_ex. It appears to be due to cache->gaia_rttopo_error_msg being freed in free_internal_cache in alloc_cache.c without having been allocated previously.Any idea how I can fix this?On the fly, no.When the structure it belongs too is being initialized, the pointer is set to NULL- after every every free, it is also set to NULL- free is done only after checking for NULLJust checked the RC1 version of the source, no changes were made in this area- everywhere where cache->gaia_rttopo_error_msg is dealt with, seems to be properly checked for (or set to) NULLI am using spatialite_alloc_connection() in src/connection_cache/alloc_cache.c to create the connection. I downloaded the source for RC1 and looked in that function and it appears neither gaia_rttopo_error_msg nor gaia_rttopo_warning_msg are set to NULL when the cache is allocated.
spatialite_alloc_reentrant
cache->gaia_rttopo_error_msg = NULL; cache->gaia_rttopo_warning_msg = NULL;
I will give it a try tomorrow. Out of time for today.Should I file a ticket against this?
--
You received this message because you are subscribed to a topic in the Google Groups "SpatiaLite Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/spatialite-users/HY6KYF1jHkQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to spatialite-use...@googlegroups.com.
To post to this group, send email to spatiali...@googlegroups.com.
Visit this group at https://groups.google.com/group/spatialite-users.
For more options, visit https://groups.google.com/d/optout.
For the record, I am compiling with the OMIT_GEOS option enabled.