2020.08.03 21:27 "[Tiff] Unable to read a large TIFF File (single image, one IFD, Strip image of size 2.6 GB) on Unix using TIFFClientOpen API", by Upanita
Goswami
- 2020.08.06 14:55 "Re: [Tiff] Unable to read a large TIFF File (single image, one IFD, Strip image of size 2.6 GB) on Unix using TIFFClientOpen API", by Upanita Goswami
- 2020.08.06 19:43 "Re: [Tiff] Unable to read a large TIFF File (single image, one IFD, Strip image of size 2.6 GB) on Unix using TIFFClientOpen API", by Bob Friesenhahn
-
2020.08.07 04:13 "Re: [Tiff] Unable to read a large TIFF File (single image, one IFD, Strip image of size 2.6 GB) on Unix using TIFFClientOpen API", by Adam
Richter
-
2020.08.10 10:00 "Re: [Tiff] Unable to read a large TIFF File (single image, one IFD, Strip image of size 2.6 GB) on Unix using TIFFClientOpen API", by Adam
Richter
- 2020.08.10 11:11 "Re: [Tiff] Unable to read a large TIFF File (single image, one IFD, Strip image of size 2.6 GB) on Unix using TIFFClientOpen API", by Upanita Goswami
-
2020.08.10 10:00 "Re: [Tiff] Unable to read a large TIFF File (single image, one IFD, Strip image of size 2.6 GB) on Unix using TIFFClientOpen API", by Adam
Richter
2020.08.06 19:30 "Re: [Tiff] Unable to read a large TIFF File (single image, one IFD, Strip image of size 2.6 GB) on Unix using TIFFClientOpen API", by Paavo Helde
Hello Upanita,
I think you expect too much from libtiff maintainers, you will have to debug your code by yourself.
If you believe you have discovered a bug in libtiff you should post a runnable program demonstrating the problem, together with any needed data. But it is much more likely that the bug is in your code. My own programs using libtiff run fine with multi-GB tiff files on both Windows and Linux, including single-strip monsters.
That said, the bug is clearly a 32-bit overflow/truncation error, as the last reported byte_read value (2147479552) is just slightly under 2^32. I suspect your data read routine truncates the correct number at some point.
Cheers
Paavo