2017.07.04 12:55 "Re: [Tiff] A bug in libtiff error/warning handling", by Even Rouault

Why can't Handler delegate to HandlerExt so that there's only ever a single handler irrespective of which call you use? Can't Handler register its own private handler with HandlerExt which strips off the thandle and calls the user-supplied handler? Internally, only the Ext variant need be invoked, with Handler wrapping it transparently.

Hum, I'm not sure we can do that (or that would be tricky) since TIFFSetErrorHandler() must return the previous handler with a type of TIFFErrorHandler. Or actually that would mess a sequence fo calls of TIFFSetErrorHandler() and then TIFFSetErrorHandlerExt(), where the later would then return our internal ErrorHandlerExt wrapper instead of NULL currently.

I've just applied Paavo's patch for now. This should fix crashing situations.

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com