Re: Problem with KWallet and JavaHL

On Mon, May 19, 2008 at 12:06 AM, Patrick Mayweg <mayweg_at_qint.de> wrote:
> Hi Mark,
> the first problem looks like a mix up of your threads. You cannot send an
> event to an object of another thread.

I do not think it is a mixup, but I am sure there are multiple threads
involved. We create and initialize the SVNClient when our Eclipse
plugin is started. Future Eclipse events that need to use it can then
happen on any thread. We made a lot of changes in the code for 1.5 to
"comply" with the threading rules. For example, we used to set
listeners and callbacks from several threads. Now we just do it once.
 SVNClient is supposed to support multiple threads and we need it to.

> For the jvm crash you should use the -verbose:jni and -Xcheck:jni flags of
> the jvm. The jvm does not check for any problems in the calls from the
> native unless you use these flags and if you should have any memory
> management problems, the crash will happen anywhere. So the output of the
> crash does not really help you.

I tried adding those flags. I did not see anything different about
the dump output. The console added a lot of messages about JNI
initialization, but I did not see anything extra that was relevant.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org