[gdal-dev] OBus error when writing GeoTiffs
Even Rouault
even.rouault at mines-paris.org
Fri Nov 14 15:25:20 EST 2008
Chris,
I'd bet too that you are hitting a problem with unaligned access on Sparc
architecture when dereferencing some pointers that is present in the
TIFFWriteDirectorySec function of the internal libtiff in GDAL 1.5.X
(I don't think that the compiler used would make any difference.)
This problem was reported and fixed as
http://bugzilla.maptools.org/show_bug.cgi?id=1892
Current internal libtiff in GDAL 1.6.0beta has the above fix and should
hopefully work.
Le Friday 14 November 2008 20:26:24 Frank Warmerdam, vous avez écrit :
> Chris Garrard wrote:
> > Hi,
> >
> > I've compiled GDAL 1.5.3 on Solaris 10, using internal support for tiff
> > and gtiff. When I try to create a new GTiff using gdal_translate, it
> > fails with "OBus Error". That's all the information I get.
> >
> > The problem is only with writing GTiffs, not reading them. I can
> > convert a tiff to another format, get information about them with
> > gdalinfo, and am using them with MapServer built with GDAL support. I
> > can write to other formats without a problem.
>
> Chris,
>
> Any chance of running things in gdb or dbx and getting a traceback?
>
> I assume this is Solaris on Sparc? Often problems on this architecture
> are byte order or "double alignment" issues.
>
> Is this a 32bit or 64 bit build? Are you using the GNU or Sun tool chains?
>
> Best regards,
More information about the gdal-dev
mailing list