[GRASS-dev] Segmentation fault with r.to.vect

GRASS GIS GRASS GIS developer
1

Hi all,

I'm trying to use r.to.vect but I got a Segmentation fault...
I'm using GRASS7 (at revision 57694) on the North Carolina dataset
[0], just enter in the user1 mapset and run:

{{{
g.region rast=elevation -p
r.watershed elevation=elevation basin=basins_10k threshold=10000
}}}

the basin_10k is fine, but if I try to convert the basin from raster
to vector I got:

{{{
r.to.vect input=basins_10k output=basins_10k type=area column=basin_num
Segmentation fault (core dumped)
}}}

Any hints? I'm the only one that have this problem?
I did the distclean and recompile everything but the error is still there...
I'm running 64bit Linux.

Pietro

[0] http://grass.osgeo.org/sampledata/north_carolina/nc_spm_08_grass7.tar.gz

2

Hi,

2013/9/15 Pietro <peter.zamb@gmail.com>:

r.to.vect input=basins_10k output=basins_10k type=area column=basin_num
Segmentation fault (core dumped)
}}}

Any hints? I'm the only one that have this problem?
I did the distclean and recompile everything but the error is still there...
I'm running 64bit Linux.

I cannot reproduce this problem (Debian GNU/Linux unstable 64bit).
Probably more detailed info (gdb output) will be needed to solve this
issue.

Cheers, Martin

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

3

On Sun, Sep 15, 2013 at 2:28 PM, Martin Landa <landa.martin@gmail.com> wrote:

Any hints? I'm the only one that have this problem?
I did the distclean and recompile everything but the error is still there...
I'm running 64bit Linux.

I cannot reproduce this problem (Debian GNU/Linux unstable 64bit).
Probably more detailed info (gdb output) will be needed to solve this
issue.

Changing the CFLAGS from:

CFLAGS="-Ofast -march=native -mfpmath=sse -flto -funroll-loops"

to:

CFLAGS="-ggdb -Wall -Werror-implicit-function-declaration"

now it is working... so it seems like the compiler over-optimize
something... :slight_smile:

Sorry for the noise.

Pietro

4

On Sun, Sep 15, 2013 at 4:23 PM, Pietro <peter.zamb@gmail.com> wrote:

On Sun, Sep 15, 2013 at 2:28 PM, Martin Landa <landa.martin@gmail.com> wrote:

Any hints? I'm the only one that have this problem?
I did the distclean and recompile everything but the error is still there...
I'm running 64bit Linux.

I cannot reproduce this problem (Debian GNU/Linux unstable 64bit).
Probably more detailed info (gdb output) will be needed to solve this
issue.

Changing the CFLAGS from:

CFLAGS="-Ofast -march=native -mfpmath=sse -flto -funroll-loops"

Try to use
-Ofast
along with
-fno-fast-math

I use (i3 processor):

MYCFLAGS="-Wall -fopenmp -lgomp -Ofast -fno-fast-math
-march=core-avx-i -fno-common -fexceptions $PENTIUM64"
MYLDFLAGS="-Wl,--no-undefined -fopenmp -lgomp"
MYCXXFLAGS="-Ofast"

Markus