[GRASS5] r.in.gdal or GDAL bug?

[Hamish]

> 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

[results]




Maybe recompile GRASS after recomiling GDAL?
If you configure with:
CFLAGS="-g -Wall" ./configure ...
then the gdb output gets a whole lot more informative.




Hamish