Hello, you are mentioning some kind of "random bug". To hunt it down, please, run failing command under valgrind, as in most of cases it indicates on an erroneous code that should be tracked down sooner than later as memory corruption quite often is hard to catch.
Running under valgrind is easy - just install it and execute "valgrind my_command with all parameters". If you have trouble understanding its output, you can ask any of us to help you. WBR, Māris. 2016-06-13 6:54 GMT+03:00 Yang, Bo (yangb2) <[email protected]>: > Dear all, > > > > Please see the link below for GSoC_2016_Additional_segmentation_algorithms > week 3 report. > > > > https://trac.osgeo.org/grass/wiki/GSoC/2016/Additional_segmentation_algorithms/weekly_report#a4June--11Juneweek3:implementmean-shiftimagesegmentationalgorithm > > > > Best, > > Bo Yang > > > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
