[GRASS-dev] GSoC weekly report 2006_0612_yb
maris.gis at gmail.com
Wed Jun 15 00:30:08 PDT 2016
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.
2016-06-13 6:54 GMT+03:00 Yang, Bo (yangb2) <yangb2 at mail.uc.edu>:
> Dear all,
> Please see the link below for GSoC_2016_Additional_segmentation_algorithms
> week 3 report.
> Bo Yang
> grass-dev mailing list
> grass-dev at lists.osgeo.org
More information about the grass-dev