AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
August 2017

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2017.08.02 15:00 "Error handling in Read/Write/Seek", by Nicolas Ruff
2017.08.02 15:26 "Re: Error handling in Read/Write/Seek", by Bob Friesenhahn
2017.08.03 15:04 "Re: Error handling in Read/Write/Seek", by Nicolas Ruff
2017.08.03 15:23 "Re: Error handling in Read/Write/Seek", by Bob Friesenhahn
2017.08.04 15:27 "Re: Error handling in Read/Write/Seek", by Even Rouault
2017.08.07 15:53 "Re: Error handling in Read/Write/Seek", by Nicolas Ruff

2017.08.02 15:26 "Re: Error handling in Read/Write/Seek", by Bob Friesenhahn

On Wed, 2 Aug 2017, Nicolas RUFF wrote:
>
> The real fix would be some kind of out-of-band error reporting (a la
> errno). Such a change would be transparent to all users of ReadOK /
> WriteOK / SeekOK macros, but I wonder if there are people in the wild
> checking return values on their own.

This is a private header so there should be no other users of these 
macros besides libtiff.

It seems best to block any negative size values from being passed into 
these functions in the first place.  Libtiff is not in control of the 
I/O functions, so it is best to assure that they are not passed 
illegal values which might cause I/O implementations to do very bad 
things.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/