2005.11.23 02:57 "Re: [Tiff] libtiff and over 4GB files", by Edward Lam
This doesn't happen to be related to this, does it?
This post is *not* about BigTIFF. Instead it is about how libtiff reports errors if the application attempts to write a file larger than 4GB. The short answer is that libtiff doesn't seem to even notice, it just writes out a corrupt file (with tile/strip offsets wrapping back to 0 at the 4GB mark).
I have created a bug on this issue at:
I am interested in feedback from folks on appropriate or inappropriate approaches to dealing with this problem. Does anyone depend on libtiff being able to write a bit past the 4GB mark? Does libtiff report errors, and I am just ignoring them somehow?