Hi,
I’m also new to GRASS and i first would thank all the community for the doc and help i have found on the web.
I’m having the same bug as#957 (#335 on old tracker). Do you have any idea if it will be fixed soon?
If it can help, i’m working on Windows7 64bits. I can reproduce the bug either on 6.4.0 or 6.4.1 .
I’ve run these commands before the bug has happened (v.voronoi on points extracted from a buffer boundary):
-v.buffer input=clc output=buffer type=boundary,area distance=500
-v.to.points -v -i input=buffer output=point_buffer type=boundary dmax=20
-v.voronoi -l input=point_buffer output=line_voronoi
If i set v.to.points with dmax=40, v.voronoi works fine on 33700 points. With dmax=20, v.voronoi bugs on 62000 points (cf. attachment)
This example has been tested on urban areas from Corine Land Cover.
The same bug happens on urban areas from Open Street Map on a smaller location, except that it happens on 1650 points with dmax=20.
It still works fine with dmax=40 (1500 points).
I have also tested v.random n=150000 like in #335, v.voronoi works fine.
Thanks in advance for your help! 
Cheers,
Vincent
(attachments)
bug_voro_20m_txtoutput.txt (1.08 KB)
