You need to log in before you can comment on or make changes to this bug.
While running tiffdump with certain tiff, code will execute with "Error while reading directory count" Magic: 0x4949 <little-endian> Version: 0x2b <BigTIFF> OffsetSize: 0x4a00 Unused: 0x1000 Directory 0: offset 8 (0x8) next 1374607638543 (0x1400d00000f) 65353 (0xff49) 11263 (0x2bff) 25289325936640< ...> 0 (0) 72 (0x48) 65536< ...> ../../libtiff_tifftump crashes/id:000002,sig:06,src:000357+000429,op:splice,rep:64: Read error accessing tag 0 value. 0 (0) IFD (13) 1718304746002688<> ../../libtiff_tifftump crashes/id:000002,sig:06,src:000357+000429,op:splice,rep:64: Seek error accessing tag 254 value. SubFileType (254) LONG8 (16) 217020518514230032<> ../../libtiff_tifftump crashes/id:000002,sig:06,src:000357+000429,op:splice,rep:64: Read error accessing tag 254 value. SubFileType (254) IFD8 (18) 9223372036854775808<> 1 (0x1) 0 (0) 845528736727072< ...> ../../libtiff_tifftump crashes/id:000002,sig:06,src:000357+000429,op:splice,rep:64: Read error accessing tag 16387 value. 16387 (0x4003) SRATIONAL (10) 1047971627009<> 3 (0x3) 0 (0) 4295164170< ...> ../../libtiff_tifftump crashes/id:000002,sig:06,src:000357+000429,op:splice,rep:64: Error while reading directory count.
Created an attachment (id=875) [details] crash seed, tiff file
what is the expected behaviour ? it the TIFF file is invalid/corrupted, tiffdump must report the errors !
Bugzilla is no longer used for tracking libtiff issues. Remaining open tickets, such as this one, have been migrated to the libtiff GitLab instance at https://gitlab.com/libtiff/libtiff/issues . The migrated tickets have their summary prefixed with [BZ#XXXX] where XXXX is the initial Bugzilla issue number.
