2017.07.05 13:41 "Re: [Tiff] A bug in libtiff error/warning handling", by Bob Friesenhahn

And where do you store that callback? You're going round in circles here :-)

By the way, thread local storage is a poor solution as it does not handle the case of several unrelated libraries using libtiff from within the same thread. Giving TIFFOpen and a few other functions which run without a TIFF handle the error handler is the proper way to fix this problem. Either that or come with with a concept of "library

Agreed. We can not predict how libtiff may be used. It may be that the same thread has many tiff handles open at once and incrementally accesses those handles. Both an error handler and an optional opaque pointer to data (which may be used by the error handler) are needed at the time the handle is opened.

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