Philip Martin <philip@codematters.co.uk> wrote on 11/02/2005 03:15:38 PM:
> JNIInit appears to attempt to do some once-only initialisation (that's
> once per application) using static variables but the code looks very
> dodgy. I don't do Java at all, and I've barely looked at the javahl
> code, but I suspect that if you can arrange for a single thread to
> call JNIInit, and allow it to complete, before any other thread gets a
> chance to race then the problem might go away. I don't know what that
> would involve in Java, perhaps it would be sufficient to construct and
> discard a temporary SVNClientSynchronized object. Do it from the
> debugger if necessary.
Not being a C programmer I cannot really comment on what that code does.
Looking at the history of the code, however, wouldn't really explain what
has changed between 1.2 and 1.3 that would cause a new problem. This code
was all present in 1.2 and earlier.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 2 21:36:27 2005