On 2011-11-16, at 10:41 , Bert Huijben wrote:
>>
>> -----Original Message-----
>> From: Philip Martin [mailto:philip.martin_at_wandisco.com]
>> Sent: woensdag 16 november 2011 16:37
>> To: Aleksandr Sidorenko
>> Cc: <users_at_subversion.apache.org>
>> Subject: Re: "Couldn't open rep-cache database" (post commit FS
>> processing)
>>
>> Aleksandr Sidorenko <asidorenko_at_cashontime.com> writes:
>>
>>> But it seems it's not this error that is triggered; it's the one a few
> lines down
>> (I changed the error message to detect it):
>>>
>>> #if APR_HAS_THREADS
>>> /* Wait for whichever thread is performing initialization to finish.
> */
>>> /* XXX FIXME: Should we have a maximum wait here, like we have in
>>> the Windows file IO spinner? */
>>> else while (status != SVN_ATOMIC_INITIALIZED)
>>> {
>>> if (status == SVN_ATOMIC_INIT_FAILED)
>>> return svn_error_create(SVN_ERR_ATOMIC_INIT_FAILURE, NULL,
>>> "Couldn't perform atomic
> initialization");
>>
>> Wow! The atomic operations are failing! Which OS? Which distribution?
>> Which complier? 32-bit or 64-bit?
>
> You get in this branch if a previous atomic initialization call failed: the
> callback function failed and returned an error. This result is then ignored
> in some code paths.
>
> It is most likely not caused by the atomic operations failing itself, but
> more likely by an initialization error in a third party library.
Any idea which library might be involved? I only used the default configuration options when building from source:
./configure --with-sqlite=/usr/local
Using sqlite 3.7.8.
Received on 2011-11-16 16:50:19 CET