2000.03.17 16:51 "Re: Some CCITT Group 3 TIFFs crash libtiff", by Jason Summers
I've encountered several CCITT Group 3-compressed TIFF images that cause programs compiled with libtiff 3.5.4 to crash with an IPF/segmentation fault.
The files are corrupt.
I agree that they are not completely valid.
(Aside: However, it's difficult to convince end users of this, since most image viewers display these files without even a warning, and the image appears correct to the naked eye.)
I've been assuming that libtiff should not crash when it encounters an invalid file. Right?
Here an error log from tiffcp (from the 3.4beta37 distribution):
RowsPerStrip (278) LONG (4) 1<4294967295> <--- where does this bogusvalue come from?
Beats me. I didn't create the files; they were sent to me by two unrelated persons. But I'd have to guess that it comes from:
Software (305) ASCII (2) 28<HylaFAX (tm) Version 4.0pl2\000>
It's conceivable that something else subsequently corrupted them, but I doubt it.