Memory access violation in OGRFeature::SetGeomField when old and new pointers refer to the same geometry
|Reported by:||dsogari||Owned by:||warmerdam|
Description (last modified by )
Perhaps this is not a naturally occurring use case scenario, but the SetGeomField? member function of OGRFeature that takes the field index as parameter is not robust, in that it does not check whether the old geometry pointer is the same as the new one. In the case that they are the same (
papoGeometries[iField] == poGeomIn) the call of the
clone() method (line 744 of ogrfeature.cpp in trunk) causes memory access violation, because the geometry's destructor is executed in the preceding delete statement (line 741 of ogrfeature.cpp).
papoGeometries[iField] to a temp variable and delete it afterwards
OGRGeometry *poOldGeometry = papoGeometries[iField]; ... delete poOldGeometry;
I guess that SetGeomFieldDirectly? should also have a similar check, despite the nonsensical nature of this use case scenario.