Opened 16 years ago
Closed 16 years ago
#2360 closed defect (fixed)
[GTiff] GTiffOddBitsBand::IWriteBlock crashes with anything different from eDataType=GDTByte
Reported by: | Even Rouault | Owned by: | Even Rouault |
---|---|---|---|
Priority: | normal | Milestone: | 1.5.3 |
Component: | default | Version: | 1.5.0 |
Severity: | normal | Keywords: | gtiff odd bits band |
Cc: |
Description
The GTiffOddBitsBand::IWriteBlock method cannot handled the following data types that are well handled by the ::IReadBlock method :
- float 16
- float 32
- int 9, ..., int 15
- int 17, ..., int 31
This can be demonstrated with the following scenario :
- cp ../autotest/gcore/data/int10.tif int10.tif
- gdalwarp ../autotest/gcore/data/int10.tif int10.tif
and the same with int24.tif, float16.tif and float24.tif
I'm wondering what is the most appropriate action as such use case is probably uncommon: preventing from opening such files in update mode (the easiest way) or adding the necessary code.
Change History (2)
comment:1 by , 16 years ago
Owner: | changed from | to
---|
comment:2 by , 16 years ago
Milestone: | → 1.5.3 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
In trunk:
It is now possible to create and translate files with GDT_UInt16 where NBITS>=9 and NBITS<=15, and with GDT_UInt32 where NBITS>=17 and NBITS<=32
All that is tested in r14841