rez@touchofmadness.com wrote (Thu, Oct 5 2006 05:35:57):
Should be fixed in CVS.
Brad,
I'm sorry but it's not. Still exactly the same problem using today's CVS.
Here's a backtrace:
$ ulimit -c 3000
$ grass63
$ v.in.ogr dsn=force_lrconnect_cl_onlycat139
output=force_lrconnect_cl_onlycat139_import
layer=force_lrconnect_cl_onlycat139
(segfault)
$ gdb v.in.ogr core
(gdb) bt
#0 0x00010101 in ?? ()
#1 0xb7cb5c2f in OGRSpatialReference::Release ()
from /usr/local/lib/libgdal.so.1
#2 0xb7cab4e7 in OGRGeometry::~OGRGeometry () from
/usr/local/lib/libgdal.so.1
#3 0xb7ca6810 in OGRCurve::~OGRCurve () from /usr/local/lib/libgdal.so.1
#4 0xb7ca6ad8 in OGRLineString::~OGRLineString ()
from /usr/local/lib/libgdal.so.1
#5 0xb7caf6ff in OGRFeature::~OGRFeature () from
/usr/local/lib/libgdal.so.1
#6 0xb7caefa5 in OGR_F_Destroy () from /usr/local/lib/libgdal.so.1
#7 0x0804ccfc in main (argc=4, argv=0xbffcb044) at main.c:744
(gdb) q
Grass or GDAL issue? Using GDAL 1.3.2+CVS 2006-07-24.
Maciek
-------------------------------------------- Managed by Request Tracker