[postgis-devel] [PostGIS] #316: IsValid called on invalid 3d object leads to crash

[PostGIS]

#316: IsValid called on invalid 3d object leads to crash
----------------------+-----------------------------------------------------
  Reporter:  pramsey  |       Owner:  mcayland     
      Type:  defect   |      Status:  closed       
  Priority:  medium   |   Milestone:  PostGIS 1.5.0
 Component:  postgis  |     Version:  trunk        
Resolution:  fixed    |    Keywords:               
----------------------+-----------------------------------------------------
Changes (by mcayland):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 I believe this is now fixed in 1.4 branch (r4902) and trunk (r4906). The
 short story is that due to the way the parser works, not all objects hold
 position information and so trying to display the error message was
 causing the crash. I've since altered the pop() function to ensure that
 the position is stored correctly in so-called "counting tuples" and then
 rebased the check functions to use these instead, except for the
 continuous curve check which seems to work slightly differently.

 Please give this a thorough test as I'm slightly concerned that I may have
 missed a few cases.

 Paul: I totally agree with you - this took much longer than it really
 should have done. I'll be the first one there standing in line with a
 pitchfork when the revolution comes.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/316#comment:4>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.