[GRASS-dev] GSoC weekly report 2006_0612_yb

GRASS GIS GRASS GIS developer
1

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

2

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) <yangb2@mail.uc.edu>:

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
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

3

On Wed, Jun 15, 2016 at 9:30 AM, Maris Nartiss <maris.gis@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

4

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.

Best,
Bo yang

-----Original Message-----
From: neteler.osgeo@gmail.com [mailto:neteler.osgeo@gmail.com] On Behalf
Of Markus Neteler
Sent: Wednesday, June 15, 2016 5:11 AM
To: Maris Nartiss <maris.gis@gmail.com>
Cc: Yang, Bo (yangb2) <yangb2@mail.uc.edu>; GRASS developers list <grass-
dev@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@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