[GRASS-dev] Re: [GRASS GIS] #1159: v.in.ascii fails with long text
file in WinGRASS-6.4.0-1
GRASS GIS
trac at osgeo.org
Mon Sep 20 15:12:37 EDT 2010
#1159: v.in.ascii fails with long text file in WinGRASS-6.4.0-1
------------------------+---------------------------------------------------
Reporter: lponti | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.1
Component: Vector | Version: 6.4.0
Keywords: v.in.ascii | Platform: MSWindows 7
Cpu: x86-32 |
------------------------+---------------------------------------------------
Comment(by glynn):
Replying to [comment:10 hellik]:
> My test mentioned above was in WinGrass65.
This issue applies to all branches and to the 6.4.0 release. And to RC7;
RC6 was the last version to use _spawnl(). All later versions are likely
to be broken on Windows, where db_shutdown_driver() will report failure.
The driver itself should terminate correctly, but the client will believe
that it failed.
Of the many calls to db_shutdown_driver(), only one actually checks the
return code. That is the one in db_close_database_shutdown_driver(), which
will return DB_FAILED.
Of the many calls to db_close_database_shutdown_driver(), only one
actually checks the return code, and that one is in v.in.ascii.
The net result is that v.in.ascii terminates with a fatal error rather
than calling Vect_build() and Vect_close().
This can be "fixed" by removing the check of the return code. We should
actually fix db_shutdown_driver(), but in the meantime, we may as well get
v.in.ascii working (and why should v.in.ascii be any different to all of
the other modules?)
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1159#comment:12>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list