#660: v.delaunay producing incorrect results -----------------------+---------------------------------------------------- Reporter: cmbarton | Owner: [email protected] 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 mmetz):
Replying to [comment:12 marisn]: > > MarkusM - what's up with those warnings in vlib/diglib code? I assume you refer to the valgrind output, at least I don't get any warnings when running v.delaunay without valgrind. The only valgrind errors that tell me something are right at the beginning, here http://trac.osgeo.org/grass/attachment/ticket/660/delaunay- valgrind1.txt#L17 and here http://trac.osgeo.org/grass/attachment/ticket/660/delaunay- valgrind1.txt#L27 The second one saying that Address 0x66d5f29 is 9 bytes inside a block of size 4,096 alloc'd may cause problems, but I have not the faintest idea where this is coming from, I don't get this one on Linux, only number 1. If all other vector modules are working, the problem is IMHO more likely somewhere in the module than in the vector libs. So, are other vector modules working? On my Linux system, v.delaunay is fast and produces correct results, also with e.g. elev_lid792_bepts with 118,716 points. Sorry, not much help from my side, Markus M -- Ticket URL: <http://trac.osgeo.org/grass/ticket/660#comment:15> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
