#1628: segfault in r.walk
----------------------------+-----------------------------------------------
Reporter: pertusus | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.4
Component: Raster | Version: svn-releasebranch64
Keywords: r.cost, r.walk | Platform: Linux
Cpu: x86-64 |
----------------------------+-----------------------------------------------
Comment(by mlennert):
Replying to [comment:8 mmetz]:
> Replying to [comment:7 mlennert]:
> > Replying to [comment:5 glynn]:
> > > Replying to [comment:3 mlennert]:
> > >
> > > > I do not have the time right now to check if this is linked to a
specific attribute or just the general number of attributes, but maybe
someone else can continue on that path ?
> > >
> > > Could it be a problem with lib/sites?
> >
> > It would seem a likely candidate, but how would that influence what is
happening a long time after the closure of the input file ? The segfault
occurs in the routine finding the cost path in which, AFAICT, the
lib/sites doesn't play a role anymore.
>
> This can happen if the sites lib corrupts some memory that is not used
by the sites lib itself. The segmentation fault can then appear anywhere
else later on. You need to use valgrind to check memory usage and search
for something like "invalid [read|write] ..." in the valgrind output,
usually rather at the beginning than at the end of the valgrind output.
I won't be able to work on this before next week, so if someone else wants
to try...
>
> Apart from that, the usage of the wrappers provided by the sites lib is
deprecated also in G6. I would suggest the replace the relevant code in
the affected modules rather than fixing the sites lib.
This sounds fairly invasive. Is this still feasible for 6.4.4 ?
Moritz
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1628#comment:9>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
