AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2004.03.03 18:01 "[Tiff] TIFFClientOpen, libtiff 3.6.1, ignores 'm' option", by Dimitar
2004.03.03 18:08 "Re: [Tiff] TIFFClientOpen, libtiff 3.6.1, ignores 'm' option", by Bob Friesenhahn
2004.03.03 18:15 "Re: [Tiff] TIFFClientOpen, libtiff 3.6.1, ignores 'm' option", by Frank Warmerdam
2004.03.03 20:48 "Re: [Tiff] TIFFClientOpen, libtiff 3.6.1, ignores 'm' option", by Andrey Kiselev

2004.03.03 18:08 "Re: [Tiff] TIFFClientOpen, libtiff 3.6.1, ignores 'm' option", by Bob Friesenhahn

I noticed that I can not open tiff files after I upgraded from libtiff 3.5.7 to 3.6.1.

The reason is TIFFClientOpen.

In 3.6.1 there is check that all client supplied function pointers are not null. However this is not enough. I am supplying 'm' option, and passing null for the last two parameters (for map and unmap) because I am not going to use memory mapped files.

I think the correct way is to check for memory mapped file related functions, only when 'm' option is not specified.

The approach which is proven to work is to provide functions which do nothing. The map function simply returns a value of zero to indicate failure.

Bob

======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen