[GRASS-dev] GSoC weekly report 2006_0612_yb

Yang, Bo (yangb2) yangb2 at mail.uc.edu
Wed Jun 15 10:21:54 PDT 2016

Hi Markus, Maris,

Thanks! It is a very useful tools for me. 
That "random bug" has been fixed for the time being (an input threshold parameter was too large previously). But I will learn to use Valgrind and let you know if I have further questions. 

Bo yang

> -----Original Message-----
> From: neteler.osgeo at gmail.com [mailto:neteler.osgeo at gmail.com] On Behalf
> Of Markus Neteler
> Sent: Wednesday, June 15, 2016 5:11 AM
> To: Maris Nartiss <maris.gis at gmail.com>
> Cc: Yang, Bo (yangb2) <yangb2 at mail.uc.edu>; GRASS developers list <grass-
> dev at lists.osgeo.org>
> Subject: Re: [GRASS-dev] GSoC weekly report 2006_0612_yb
> On Wed, Jun 15, 2016 at 9:30 AM, Maris Nartiss <maris.gis at gmail.com> wrote:
> > 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".
> See also here:
> https://grasswiki.osgeo.org/wiki/GRASS_Debugging#Using_Valgrind
> > If you have trouble understanding its
> > output, you can ask any of us to help you.
> >
> > WBR,
> > Māris.
> best,
> Markus

More information about the grass-dev mailing list