[GRASS-dev] GSoC weekly report 2006_0612_yb
neteler at osgeo.org
Wed Jun 15 02:11:13 PDT 2016
On Wed, Jun 15, 2016 at 9:30 AM, Maris Nartiss <maris.gis at gmail.com> wrote:
> 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".
See also here:
> If you have trouble understanding its
> output, you can ask any of us to help you.
More information about the grass-dev