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

JavaHL problems with 1.2 RC1

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-04-13 21:22:39 CEST

I have started to look at JavaHL in 1.2 so that we can put some 1.2
features, like locking into Subclipse. I am having trouble getting
started. This is all on Windows.

I have been building my own custom version of JavaHL for quite a while for
my own purposes. I use VS .NET and I eliminate a lot of the dependencies
that I do not need. I think I know what I am doing. Since I was having
problems, I decided to do a stock Subversion build using the same setup
that would be done for the "official binaries". Unfortunately, I get the
exact same problems which leads me to believe that the problem is not me.

It looks like the problem is some of the older method signatures are
failing. For example, many of the methods have had a parameter added to
indicate if svn:externals should be processed. Until I get in there and
change the code, Subclipse is using the 1.1 signatures, which should still
work. I am getting an error like this which crashed my JVM:

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at
PC=0x3AA2F98
Function=[Unknown.]
Library=C:\subclipse\javahl-win32\libsvnjavahl-1.dll

NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.

Current Java thread:
        at org.tigris.subversion.javahl.SVNClient.status(Native Method)
        at
org.tigris.subversion.javahl.SVNClient.status(SVNClient.java:127)
        at
org.tigris.subversion.javahl.SVNClientSynchronized.status(SVNClientSynchronized.java:96)
        - locked <0x14d2ff98> (a java.lang.Class)
        at
org.tigris.subversion.svnclientadapter.javahl.JhlClientAdapter.getStatus(JhlClientAdapter.java:517)
        at
org.tigris.subversion.svnclientadapter.javahl.JhlClientAdapter.getStatus(JhlClientAdapter.java:496)
        at
org.tigris.subversion.subclipse.core.status.RecursiveStatusUpdateStrategy.updateStatus(RecursiveStatusUpdateStrategy.java:56)

If I change Subclipse to use the new status signature I get by this
problem, but then get the same problem when I try to do an update.

Short of a major JavaHL problem, the only thing I can think of is that I
have switched Subclipse to use the Notify2 class. Is that some signal to
JavaHL to only use the newest methods? Looking at the JavaHL code, I
would think not.

I am not sure how to proceed or interpret these problems.

Thanks

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. 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 Apr 13 21:23:23 2005

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