[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Is svn_config_get() not thread-safe?

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Wed, 26 Mar 2008 01:44:22 -0400

"David Glasser" <glasser_at_davidglasser.net> writes:
>> The implementation bears out the doc string's claim. (See the code
>> below, with notes from me marked with "###".) But this is bogosity:
>> another thread could call svn_config_get() and wipe out *valuep before
>> the first caller ever has a chance to "consume" (e.g., copy) the value.
> Well, specifically it's "the next call to svn_config_get() with the
> same svn_config_t". Does that make it any better?

Well, the doc string should state that too, but no, it doesn't nmake the
problem go away. It remains the case that there is no thread-safe way
to extract a value -- two different threads could have the same config
object, there's no rule against that (nor should there be).

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-26 06:45:05 CET

This is an archived mail posted to the Subversion Dev mailing list.