[GRASS-user] Trouble with (gdalwarp) r.in.wms ubder Ubuntu 64bit
hamish_b at yahoo.com
Sun Jun 15 04:14:33 EDT 2008
Nikos Alexandris wrote:
> [ I assume this has to again with variables, paths and
> similar in which I still don't understand fully. Isn't there a
> way to set this by default when installing GRASS (or gdaltools)? ]
I am not sure what you mean to set?
Did you compile/install gdal by hand or from distributed binary packages?
> Under Ubuntu64bit I get some trouble with r.in.gdal
> (actually gdalwarp):
> r.in.wms mapserver="$SERVER" layer=UK500
> out=UK500_Bavaria.3 format=tiff
> Calculating tiles
> Requesting 1 tiles.
> Downloading tiles
> Tile already downloaded
> All tiles downloaded successfully
> Creating output file that is 572P x 662L.
> Processing input
> Using band 4 of source image as alpha.
> Using band 4 of destination image as alpha.
> 0...10...20...30...40...50...60...70...80...90...100 -
> *** glibc detected *** gdalwarp: double free or corruption
> 0x0000000000611a10 ***
this is a memory handling error in gdalwarp.
what version of GDAL?
you could try using gdalwarp by itself on the command line with the saved input file /home/nik/grassdb/rlp_fgaps/wms_download/UK500_Bavaria.3__0.tiff
and see how it goes? If that still fails, file a gdal bug.
> ======= Backtrace: =========
> ERROR: r.in.gdalwarp: gdalwarp failure.
> ERROR: Raster map <UK500_Bavaria.3> not found in
> current mapset
currently in r.in.wms I don't know how to test to see if r.in.gdalwarp failed (it is called with eval), and so the r.in.wms script continues on as if it always works.
More information about the grass-user