[GRASS-dev] Re: [GRASS GIS] #1276: r.null in winGRASS does not work
properly
GRASS GIS
trac at osgeo.org
Fri Jan 27 04:36:31 EST 2012
#1276: r.null in winGRASS does not work properly
------------------------------+---------------------------------------------
Reporter: helena | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone: 6.4.2
Component: Raster | Version: 6.4.1 RCs
Keywords: r.null, wingrass | Platform: MSWindows 7
Cpu: Unspecified |
------------------------------+---------------------------------------------
Comment(by hamish):
Replying to [comment:14 hamish]:
> ... next step will be to add 'errno' reporting to the failed
> remove() prior 'cell' file message while rerunning v.to.rast
> with --overwrite.
ok, with `perror(path)` in place I see `.../cell/mapname: Permission
denied.` Checking in the Windows Task Manager I see that a leftover
dbf.exe and cmd.exe are still running after v.to.rast has finished.
If I kill the dbf.exe the cmd.exe goes away too, then r.null seems to
work. I'm not sure why dbf.exe would have the cell file open, I guess it
is actually the residual cmd.exe which is doing that. (?)
Interestingly with r.null I just get the perror() message but not the
G_warning() from the failed remove(). !?
we saw this same zombie dbf.exe problem before in #1184. In that case
Martin discovered `db_close_database_shutdown_driver()` wasn't called. It
looks like v.to.rast has the same problem: hopefully r50487 (devbr6) fixes
it.
Hamish
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1276#comment:15>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list