AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2011.05.05 16:44 "[Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Katerina Sedivy
2011.05.05 15:03 "[Tiff] Access Violation on TiffClose()", by Katerina Sedivy
2011.05.05 15:27 "Re: [Tiff] Access Violation on TiffClose()", by Olivier Paquet
2011.05.05 16:02 "Re: [Tiff] Access Violation on TiffClose()", by Katerina Sedivy
2011.05.05 16:22 "Re: [Tiff] Access Violation on TiffClose()", by Olivier Paquet
2011.05.05 17:42 "Re: [Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Frank Warmerdam
2011.05.05 19:01 "Re: [Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Bob Friesenhahn
2011.05.05 19:49 "Re: [Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Katerina Sedivy
2011.05.05 20:16 "Re: [Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Bob Friesenhahn
2011.05.06 17:07 "Re: [Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Katerina Sedivy
2011.05.12 06:09 "Re: [Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Andreas Kleinert
2011.05.05 19:59 "Re: [Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Katerina Sedivy
2011.05.05 21:08 "Re: [Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Frank Warmerdam

2011.05.05 20:16 "Re: [Tiff] Is LibTiff 3.9.5 Thread Safe ?", by Bob Friesenhahn

<<a bunch of threads requested to open different TIFF files all at the same
time>>
This is exactly my case

<<the library has been exercised at least once>> What do you mean by exercised?

For example, reading or writing a file.

There is no specific thread-safety code in libtiff. The code is written to be re-entrant but there are still some static variables.

On some systems, it is necessary to build code with particular options in order to be thread safe (e.g. C library functions may otherwise not be thread safe). Libtiff does not (by itself) provide any such build options.

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