2005.11.23 02:32 "[Tiff] libtiff and over 4GB files", by Frank Warmerdam

2005.11.23 13:36 "Re: [Tiff] libtiff and over 4GB files", by Frank Warmerdam

On 11/22/05, Bob Friesenhahn <bfriesen@simple.dallas.tx.us> wrote:

Detection of invalid offsets could be an interesting proposition on 32-bit systems which don't support large files. Detection of rollover on a 32-bit integer may be a challenge to reliably implement. Sometimes the off_t type supports 2GB access while other times it supports terrabytes. Hopefully the system libraries are reliable at reporting writes beyond what is supported.


We are already dependent on using a "64bit" file IO API in order to reliably handle files in the 2-4GB range. So, as long as we have a large file API it should be easy to determine if we have moved past 4GB. If we are using an old "signed 32bit" file API then we are hosed for big files anyways.

Best regards,

I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent