[postgis-devel] [PostGIS] #210: segmentation faults in lwgeom_geos.c:pgis_union_geometry_array

[PostGIS]

#210: segmentation faults in lwgeom_geos.c:pgis_union_geometry_array
------------------------+---------------------------------------------------
  Reporter:  dfuhriman  |       Owner:  robe         
      Type:  defect     |      Status:  assigned     
  Priority:  medium     |   Milestone:  postgis 1.3.7
 Component:  postgis    |     Version:  trunk        
Resolution:             |    Keywords:               
------------------------+---------------------------------------------------
Comment (by mcayland):

 Replying to [comment:23 robe]:

 > More update.  This does not return same result as my old install.

 Yes, this is correct. In the old code, PostGIS would run off the end of
 the array for each NULL row encountered by the aggregate. Now depending on
 what was previously in the array, this would either point to a random
 geometry from elsewhere in the query, or otherwise to a random part of
 memory causing a segfault.

 So in short, I would expect any query containing NULLs that doesn't crash
 to return a wrong answer in 1.3 - however what is important is that
 queries that don't contain NULLs still return the same answer for both 1.3
 and 1.4 with this patch.


 HTH,

 Mark.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/210#comment:25>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS