Bug 2407 – Cannot read signed long

Bug 2407 - Cannot read signed long

Summary:

Cannot read signed long

Status:	RESOLVED LATER

Product:	libtiff
Component:	default
Version:	4.0.1
Platform:	PC Windows NT

Importance:	P2 enhancement
Target Milestone:	---
Assigned To:	Frank Warmerdam

URL:
Whiteboard:
Keywords:	migrated_to_gitlab

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-08-24 00:38 by yimin.uci@gmail.com
Modified:	2019-10-01 14:19 (History)

Attachments
Proposal patch (16.93 KB, patch) 2017-05-16 06:40, Natsuki Kawai	Details \| Diff
Test fo the patch (3.53 KB, text/x-csrc) 2017-05-16 06:43, Natsuki Kawai	Details
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From yimin.uci@gmail.com 2012-08-24 00:38:39

Libtiff cannot read a signed integer(TIFF_SLONG) from a tiff file, but it can
read an unsigned one(TIFF_LONG).

A test case is included. The output I got is:

Done write.
TEST_TAG value: 0x1234
Read TEST_TAG_NOT_WOKING value failed.
Done read.

------- Comment #1 From Even Rouault 2017-01-11 15:17:00 -------

There's no test case attached to this ticket

------- Comment #2 From Natsuki Kawai 2017-05-16 06:40:51 -------

Created an attachment (id=775) [details]
Proposal patch

I encountered a similar problem.
The cause is that functions for reading signed integer fields are not
implemented on tif_dirread.c.

------- Comment #3 From Natsuki Kawai 2017-05-16 06:43:02 -------

Created an attachment (id=776) [details]
Test fo the patch

------- Comment #4 From Even Rouault 2019-10-01 14:19:37 -------

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.