Return-Path: <tiff-bounces@remotesensing.org>
Received: from inav002.isp.belgacom.be (inav002.isp.belgacom.be [195.238.3.145])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id iA4JKHgD016081
        for <joris.at.lebbeke@skynet.be>; Thu, 4 Nov 2004 20:20:17 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from inas015.isp.belgacom.be (localhost [127.0.0.1])
        by inav002.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id iA4JK9XB013833
        for <joris.at.lebbeke@skynet.be>; Thu, 4 Nov 2004 20:20:09 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from inmx012.isp.belgacom.be (inmx012.isp.belgacom.be [195.238.3.90])
        by inas015.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id iA4JJvmC018491
        for <joris.at.lebbeke@skynet.be>; Thu, 4 Nov 2004 20:20:00 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx012.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id iA4JJncU004338
        for <joris.at.lebbeke@skynet.be>; Thu, 4 Nov 2004 20:19:51 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id A295D447BC8; Thu,  4 Nov 2004 14:19:35 -0500 (EST)
X-Original-To: Tiff@remotesensing.org
Delivered-To: Tiff@remotesensing.org
Received: from scooby.simplesystems.org (scooby.simplesystems.org
	[65.66.246.67])
	by xserve.flids.com (Postfix) with ESMTP id A73BA447BA5
	for <Tiff@remotesensing.org>; Thu,  4 Nov 2004 14:19:33 -0500 (EST)
Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74])
	by scooby.simplesystems.org (8.12.10+Sun/8.12.10) with ESMTP id
	iA4JJWjt021060; Thu, 4 Nov 2004 13:19:32 -0600 (CST)
Date: Thu, 4 Nov 2004 13:19:31 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@blade.simplesystems.org
To: Chris Losinger <losinger@earthlink.net>
Subject: Re: [Tiff] is libtiff thread-safe?
In-Reply-To: <6.0.0.22.1.20041104140811.02611f48@pop.earthlink.net>
Message-ID: <Pine.SOC.4.60.0411041311570.9670@blade.simplesystems.org>
References: <LOENLAKPHCMDKNAAGBHCAEEECAAA.jxu@cvisiontech.com>
	<Pine.SOC.4.60.0411041303330.9670@blade.simplesystems.org>
	<6.0.0.22.1.20041104140811.02611f48@pop.earthlink.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Tiff@remotesensing.org
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: 165734aa4b271ead226431fcf110c7db

On Thu, 4 Nov 2004, Chris Losinger wrote:

>        oh?
>
>        that's an unpleasant thing to learn.
>
>        are there any plans to make it thread safe?

There was some discussion on the list (initiated by Joris I think) 
regarding proposed improvements to the error reporting APIs to make 
them easier to use with threads.

It seems that libtiff is currently thread-agnostic.  It doesn't do 
anything special to support threads, however, it is not a disaster 
either since its implementation is mostly re-entrant.

In some target environments, libtiff should be specially compiled to 
ensure that its use of C library APIs (and global errno) is thread 
safe.  I don't believe that this special compilation support exists 
yet.

Bob

>
>
> At 02:04 PM 11/4/2004, you wrote:
>> On Thu, 4 Nov 2004, James Xu wrote:
>> 
>>> Does anyone know if the latest version of libtiff is thread-safe?
>>> I looked all over the internet and couldn't find the answer.
>>> I looked through some of the code and it didn't look thread-safe.
>> 
>> There is clearly code in libtiff which is not thread safe.  The 
>> error-reporting mechanism is not thread safe (or is at least 
>> thread-unfriendly).
>> 
>> Bob
>
> __________________________
> Chris Losinger
> Smaller Animals Software, Inc. 
> http://www.smalleranimals.com
>
>
> _______________________________________________
> Tiff mailing list
> Tiff@remotesensing.org
> http://xserve.flids.com/mailman/listinfo/tiff
>

======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen
_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
