#1308: wingrass - dbf.exe-crash
---------------------------------------+------------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 6.4.1
Component: Default | Version: svn-releasebranch64
Keywords: wingrass, dbf.exe, d.vect | Platform: MSWindows Vista
Cpu: x86-32 |
---------------------------------------+------------------------------------
Comment(by martinl):
Replying to [ticket:1308 hellik]:
> some additional informations (delivered by DEUBUG=5 and windows-crash-
informations:
>
{{{
> D1/5: grass.script.core.start_command(): g.mlist -m type=vect
> D1/5: grass.script.core.start_command(): v.db.connect -g
map=lakes@PERMANENT fs=;
> D1/5: grass.script.core.start_command(): db.describe -c table=lakes
driver=dbf database=C:\gisdata\grassdata\nc_spm_08\PERMANENT\dbf\
> GRASS 6.4>
> GRASS 6.4> D1/5: grass.script.core.start_command(): d.vect --q
map=lakes@PERMANENT type=point,area,face,centroid,line,boundary
> D1/5: grass.script.core.start_command(): g.pnmcomp opacity=1.0
mask=c:\users\syringia\appdata\local\temp\tmp5rhzes.pgm height=502
width=782 background=255:255:255:255
input=c:\users\syringia\appdata\local\temp\tmp5rhzes.ppm
output=c:\users\syringia\appdata\local\temp\tmpo5cnsd.ppm
> D1/5: grass.script.core.start_command(): g.findfile -n file=MASK
element=cell
}}}
it doesn't seem to be full debug output, I can see only debug messages
produced by python library...
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1308#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
