[GRASS-dev] Re: [GRASS GIS] #660: v.delaunay producing incorrect results

GRASS GIS trac at osgeo.org
Sat Jan 2 13:19:32 EST 2010


#660: v.delaunay producing incorrect results
-----------------------+----------------------------------------------------
  Reporter:  cmbarton  |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect    |      Status:  new                      
  Priority:  critical  |   Milestone:  6.4.0                    
 Component:  Vector    |     Version:  6.4.0 RCs                
Resolution:            |    Keywords:  delaunay                 
  Platform:  MacOSX    |         Cpu:  OSX/Intel                
-----------------------+----------------------------------------------------
Comment (by kyngchaos):

 1) yes, I remember memory issues when running the old v.delaunay on a
 large number of points.

 2) not me, I can tinker, but don't know C well enough for this sort of
 task ;)

 3) No change (both 32 and 64bit).  No compile errors before or after the
 patch :(

 I can run it thru GDB, though I've only ever used that once thru the Xcode
 GUI.  Any suggestions what I might look at/for?  Is there an automatic
 trace that can be generated (minimal entry of gdb commands) that can be
 compared with Linux?

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/660#comment:24>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list