[GRASS-dev] v.what.rast: topology really necessary?

Martin Landa landa.martin at gmail.com
Tue Jan 10 06:38:47 PST 2017


2017-01-10 13:18 GMT+01:00 Blumentrath, Stefan <Stefan.Blumentrath at nina.no>:
> Thanks for your swift relpy. Unfortunately, without topology, v.what.rast segfaults in r70332.
> v.external --overwrite input=PG:dbname=gisdata layer=points output=points_pg73ot -bo
> v.what.rast map=points_pg73ot raster=rand column=morphology
> Reading features from vector map...
> Segmentation fault (core dumped)

hm, I can confirm it. Unfortunately it's something hidden. It segfaults at

#4  0x00007ffff7ba5d5d in get_feature (Map=0x7fffffffbed0, fid=-1,
type=-1) at read_pg.c:614
#5  0x00007ffff7ba5829 in read_next_line_pg (Map=0x7fffffffbed0,
line_p=0x63b3e0, line_c=0x60ad70, ignore_constraints=0) at

when I comment out this line, it segfauls on completely different place:

#7  0x00007ffff729e187 in G__calloc (file=0x7ffff72e21a0
"lib/gis/parser.c", line=658, m=1024, n=1) at alloc.c:81
#8  0x00007ffff72c243b in recreate_command (original_path=0) at parser.c:658
#9  0x00007ffff72c2b77 in G_recreate_command () at parser.c:802

It seems to be memory issue. Please report an issue in trac. Ma

Martin Landa

More information about the grass-dev mailing list