[Gdal-dev] GDAL 1.3.0 Beta1 Released

[Alessandro Amici]

Frank,

On Sunday 07 August 2005 22:49, Frank Warmerdam wrote:
> In lead up to a GDAL 1.3.0 release, I have prepared a first beta
> release.  It is available at:

ugh! i noticed the announce just after having tested on current cvs, hope they 
are not that different...


being back to the remote sensing/gis business (at least for a while) i'm 
writing a tiny python/qt application on top of gdal and i hit the following 
bug with both debian gdal-1.2.6 and current cvs (--with-threads).

i open a bunch of tif files and gdal behaves quite reasonably within the same 
function, i.e. i can use GetRasterBand().ReadAsArray normally.

then if i try to access the gdal.Band objects from within a qt button click 
handler i get random errors and random segfault's as soon as i try to 
ReadAsArray.

example errors are ('raster of' numbers change):
ERROR 5: Access window out of range in RasterIO().  Requested
(0,0) of size 10x10 on raster of -216068892x23625214.

and the segfault appears to be inside the locking code:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1210644800 (LWP 22483)]
0xb7856faa in GDALRasterBand::TryGetLockedBlockRef () 
from /usr/local/lib/libgdal.so.1
(gdb)

the pythonic attributes of gdal.Band work as usual, so i'm inclined to think 
this might be a memory corruption bug possibly due to threading-problems.

with the same files i can reproduce the problem within the python interpreter.

cheers,
alessandro

-- 
B-Open Solutions srl - http://www.bopen.it/