[GRASS-user] v.random segfault

Hi guys, I have encountered an error using v.random. It segfaults whenever I try to create some random points. > gdb v.random (gdb) run output=test_points npoints=6 restrict=test column=Depth --v --o Starting program: /usr/local/grass78/bin/v.random output=test_points npoints=6 restrict=test

Re: [GRASS-user] r.param.scale issue

Markus, Māris, and others who feel concerned, following on with this post, I am wondering if either something is wrong with my openMP install (then it's not the place to bother anyone with it) or if there may be something wrong with r.param.scale, and possibly more generally with the way GRASS

Re: [GRASS-user] r.param.scale issue

Recompiled without openmp: md5sum Bureau/slope_test.* 1231556eb6c1307834d3eb0c41108982 Bureau/slope_test.1 1231556eb6c1307834d3eb0c41108982 Bureau/slope_test.10 1231556eb6c1307834d3eb0c41108982 Bureau/slope_test.11 1231556eb6c1307834d3eb0c41108982 Bureau/slope_test.12

Re: [GRASS-user] r.param.scale issue

On Thu, Oct 15, 2020 at 10:58 AM Vincent Bain wrote: > > Markus, > my configuration cmd : > > ./configure ... > --with-openmp=yes ... > --with-openmp You may drop "openmp" and recompile (after "make distclean"). Just to exclude that openMP causes the trouble. Markus

Re: [GRASS-user] r.param.scale issue

Markus, my configuration cmd : ./configure --with-freetype --with-freetype-includes=/usr/include/freetype2 --with-postgres --with-postgres-includes=/usr/include/postgresql/ --with-postgres-libs=/usr/lib/postgresql --with-readline --with-geos --with-liblas=yes --with-cairo

Re: [GRASS-user] r.param.scale issue

Markus, my configuration cmd : ./configure --with-freetype --with-freetype-includes=/usr/include/freetype2 --with-postgres --with-postgres-includes=/usr/include/postgresql/ --with-postgres-libs=/usr/lib/postgresql --with-readline --with-geos --with-liblas=yes --with-cairo

Re: [GRASS-user] r.param.scale issue

Hi Vincent, On Thu, Oct 15, 2020 at 10:13 AM Vincent Bain wrote: > > Thanks Māris for your advice, > > it sounds dreadful to me to have to deal with these hardware issues... > I installed valgrind and ran r.param.scale. > > Attached are the outputs of the command, first run without any >

Re: [GRASS-user] r.param.scale issue

Thanks Māris for your advice, it sounds dreadful to me to have to deal with these hardware issues... I installed valgrind and ran r.param.scale. Attached are the outputs of the command, first run without any argument, then with --leak-check=full option. Of course it's nearly "doubledutch" to me!

Re: [GRASS-user] r.param.scale issue

Hello Vincent, start with running stress tests on your hardware. I always run at least 24h memtest followed by several rounds of compiling kernel on any new hardware. Allowed to catch a misbehaving motherboard of laptop before I started to use it for my daily needs. You could try to run process

Re: [GRASS-user] r.param.scale issue

Hi Markus, thank you for your reply and investigation! just in case, if I follow your first method, here's what it gives me on a 12 steps loop, i.e. 40% success : md5sum Bureau/slope_test.* 0bfb867317c149e9eb0b232ed6859294 Bureau/slope_test.1 872be645bdcc826442010e0f7cdcf8b3