Re: [gdal-dev] a possible memory leak in ogr\ogrsf_frmts\sqlite

2025-02-06 Thread Deyan Vasilev via gdal-dev
Hello, it may be needed for sure for the whole session or at least if you need the already registered extension to be available at the next db open attempt. A deeper look in sqlite3 gave me the sqlite3_shutdown() API that actually frees the extension attached via sqlite3_reset_auto_extension() to

Re: [gdal-dev] a possible memory leak in ogr\ogrsf_frmts\sqlite

2025-02-06 Thread Even Rouault via gdal-dev
Le 06/02/2025 à 12:30, Deyan Vasilev a écrit : Hello, it may be needed for sure for the whole session or at least if you need the already registered extension to be available at the next db open attempt. A deeper look in sqlite3 gave me the sqlite3_shutdown() API that actually frees the extens

[gdal-dev] GDAL open flags

2025-02-06 Thread Michał Kowalczuk via gdal-dev
Hi GDAL devs, does anyone know why GDAL_OF_ALL and GDAL_READONLY consts have the same value? Both are used by GDALOpenEx as nOpenFlags param so shouldn't they be distinguishable? *#define GDAL_OF_READONLY 0x00* *#define GDAL_OF_ALL 0x00* https://github.com/OSGeo/gdal/blob/5248a30e9a84998dd0416ab7

Re: [gdal-dev] GDAL open flags

2025-02-06 Thread Michał Kowalczuk via gdal-dev
It make sense. If I find an unusual case, I'll write here :-) Thanks! czw., 6 lut 2025 o 09:19 Javier Jimenez Shaw napisał(a): > I would say that 0 is the default. Read only and all drivers. > If you want anything else, then specify it. > > On Thu, 6 Feb 2025, 09:10 Michał Kowalczuk via gdal-dev

Re: [gdal-dev] GDAL open flags

2025-02-06 Thread Javier Jimenez Shaw via gdal-dev
I would say that 0 is the default. Read only and all drivers. If you want anything else, then specify it. On Thu, 6 Feb 2025, 09:10 Michał Kowalczuk via gdal-dev, < gdal-dev@lists.osgeo.org> wrote: > Hi GDAL devs, > does anyone know why GDAL_OF_ALL and GDAL_READONLY consts have the same > value?

[gdal-dev] a possible memory leak in ogr\ogrsf_frmts\sqlite

2025-02-06 Thread Deyan Vasilev via gdal-dev
Hello, I was chasing for a long time a small 8 byte memory leak and was able to identify it in the OGR sqlite extension binding, here's what I observed: A call to OGRSQLiteBaseDataSource::OpenOrCreateDB() would invoke OGR2SQLITE_Register() and then sqlite3_auto_extension(). The latter is a sqlite

Re: [gdal-dev] a possible memory leak in ogr\ogrsf_frmts\sqlite

2025-02-06 Thread Even Rouault via gdal-dev
Deyan this sounds more like "still reachable" memory in Valgrind terminology (https://valgrind.org/docs/manual/faq.html#faq.deflost), that is memory that is allocated by some component, still reachable by it but never explicitly freed before the end of the process, and the amount of it doesn'

[gdal-dev] Call for review on RFC 107: Add OGRLayer::IGetExtent() and OGRLayer::ISetSpatialFilter()

2025-02-06 Thread Even Rouault via gdal-dev
Hi, Please review https://github.com/OSGeo/gdal/pull/11814: Add OGRLayer::IGetExtent() and OGRLayer::ISetSpatialFilter() It could have gone through a pull request business-as-usual, but as this impacts a number of drivers, including out-of-tree ones, this is worth this small RFC. Summary -

[gdal-dev] GDAL-GRASS GIS driver 1.0.3 released

2025-02-06 Thread Nicklas Larsson via gdal-dev
The GDAL-GRASS driver 1.0.3 provides more than 25 improvements and fixes with respect to the release 1.0.2. Highlights: - CMake support added - Autoconf configure updated to version 2.71, with a number of fixes - Migrate use of deprecated GDAL driver registration API - Remove use of obsolete CPL_