gdalinfo segfault on ASTER 30m DEM GeoTIFF

[Markus Neteler]

Hi Frank,

sorry to say, but gdalinfo crashes on ASTER 30m DEM GeoTIFF data.

strace gdalinfo ASTER_DEM20011211140106.tif
[...]
open("/lib/mmx/avgridio.dll", O_RDONLY) = -1 ENOENT (No such file or
directory)
stat64("/lib/mmx", 0xbfff3750)          = -1 ENOENT (No such file or
directory)
open("/lib/avgridio.dll", O_RDONLY)     = -1 ENOENT (No such file or
directory)
stat64("/lib", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/usr/lib/avgridio.dll", O_RDONLY) = -1 ENOENT (No such file or
directory)
munmap(0x40040000, 85250)               = 0
stat64("ASTER_DEM20011211140106.tif", {st_mode=S_IFREG|0644,
st_size=13436332, ...}) = 0
open("ASTER_DEM20011211140106.tif", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=13436332, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x40040000
read(3, "II*\0\0\352\314\0j\377j\377j\377j\377j\377j\377j\377j\377"...,
4096) = 4096
_llseek(3, 0, [0], SEEK_SET)            = 0
open("ASTER_DEM20011211140106.tif", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=13436332, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x40041000
read(4, "II*\0\0\352\314\0j\377j\377j\377j\377j\377j\377j\377j\377"...,
4096) = 4096
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++


As a small compensation: All processed ASTER DEM data (30m) which are available
from USGS in HDF format, are also placed in Geotiff here:
ftp://152.61.128.25/pub/asterdem/relative/

An incredible source! I found that today here:
http://www.terrainmap.com/rm23.html#top

Perhaps you can look into the problem, I have uploaded the file to
the gdal-incoming.

Best regards

 Markus

[warmerdam]

Markus,

The file works fine with gdalinfo and OpenEV here.  Could you try
doing a CVS update and rebuild, also insuring you are using internal
libtiff and libgeotiff?  There was a problem in the tiff support in
CVS that I fixed a day or two ago and it may be what is causing your problem.

[warmerdam]

I assume this was some sort of build problem.