[GRASS5] r.in.gdal or GDAL bug?
Otto Dassau
otto.dassau at gmx.de
Thu Feb 10 06:56:43 EST 2005
On Thu, 10 Feb 2005 11:52:44 +1300
Hamish <hamish_nospam at yahoo.com> wrote:
> > I compiled GDAL from CVS today and tried to import landsat data:
> >
> >
> > Problem:
> >
> > following happens without using paramter -o:
> >
> > r.in.gdal in=p192r027_7k20000620_z33_nn61.tif out=p192r027nn61
> > A datum name wgs84 (WGS_1984) was specified without transformation
> > parameters.
> > Note that the GRASS default for wgs84 is towgs84=0.000,0.000,0.000.
> > Segmentation fault
> >
> >
> > with parameter -o import with r.in.gdal works:
> ...
>
>
> maybe you can run it through a debugger and post the results of a
> back-trace?
>
>
> gdb `which r.in.gdal`
> ...
> (gdb) run in=p192r027_7k20000620_z33_nn61.tif out=p192r027nn61
> ...
> Segmentation fault
> (gdb) bt
>
hi,
results:
(gdb) run in=p192r027_7k20000620_z33_nn61.tif out=muell
Starting program: /usr/local/grass-6.0.cvs/bin/r.in.gdal in=p192r027_7k20000620_z33_nn61.tif out=muell
(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 1086230496 (LWP 4835)]
ERROR 1: /usr/local/lib/gdal_GRASS.so: undefined symbol: _ZN11GDALDataset10AdviseReadEiiiiii12GDALDataTypeiPiPPc
ERROR 1: /usr/local/lib/gdal_GRASS.so: undefined symbol: _ZN11GDALDataset10AdviseReadEiiiiii12GDALDataTypeiPiPPc
A datum name wgs84 (WGS_1984) was specified without transformation parameters.
Note that the GRASS default for wgs84 is towgs84=0.000,0.000,0.000.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1086230496 (LWP 4835)]
0x405f7781 in ____strtod_l_internal () from /lib/tls/libc.so.6
(gdb)
does this help?
Otto
More information about the grass-dev
mailing list