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

RE: javahl crashes virtual machine on Windows

From: GOVAERTS Lieven <Lieven.GOVAERTS_at_post.be>
Date: 2005-08-03 11:22:12 CEST

Update:

 

I'm pretty sure this is a bug in JavaHL, or, a missing test for a situation that probably doesn't happen on many

other repositories.

 

If I do an svn log on the same target, I see some of these in the result:

 

r58 | (no author) | (no date) | 1 line

 

 

------------------------------------------------------------------------

r57 | (no author) | (no date) | 1 line

 

 

------------------------------------------------------------------------

r56 | (no author) | (no date) | 1 line

 

This situation occurs because the target is world readable, but some of its children need authentication for read

access. Subversion ( or apache ) will probably check the target branch, see that it's readable and

doesn't ask for user & password anymore, and fails to get author/commit message info.

 

As soon as I manage to build the win32 version I'll make a patch and post it to the dev group.

 

Regards,

 

Lieven.

 

  _____

From: GOVAERTS Lieven [mailto:Lieven.GOVAERTS@post.be]
Sent: woensdag 3 augustus 2005 10:42
To: users@subversion.tigris.org
Subject: javahl crashes virtual machine on Windows

 

Hi,

 

 

I'm working on a program to do reporting of our SVN repositories. First test was to extract the log messages

from the repositories using JavaHL.

 

I'm using Subversion and downloaded the JavaHL bindings for windows from the tigris.org website.

 

My test code is something like this:

 

  client = new SVNClient();

    

  LogMessage[] lms = client.logMessages("http://example.com/svn/test", null, null);

 

When I did this on our test repository, all went well, but on one of our ( very small ) production repositories,

It will crash the whole VM. It did write a core dump, which I've attached here.

 

Ideas anyone?

 

Regards,

 

Lieven.

 

  _____

STRICTLY PERSONAL AND CONFIDENTIAL
This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies.

Dit bericht is enkel bestemd voor de aangeduide ontvangers en kan vertrouwelijke informatie bevatten. Als u niet de ontvanger bent, dan mag u de inhoud van dit bericht niet bekendmaken noch kopiëren. Als u dit bericht per vergissing ontvangen heeft, gelieve er de afzender of De Post onmiddellijk van op de hoogte te brengen en het bericht vervolgens te verwijderen.

Ce message est uniquement destinĂ© aux destinataires indiquĂ©s et peut contenir des informations confidentielles. Si vous n'ĂȘtes pas le destinataire, vous ne devez pas rĂ©vĂ©ler le contenu de ce message ou en prendre copie. Si vous avez reçu ce message par erreur, veuillez en informer l'expĂ©diteur, ou La Poste immĂ©diatement, avant de le supprimer.

STRICTLY PERSONAL AND CONFIDENTIAL
This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies.

Dit bericht is enkel bestemd voor de aangeduide ontvangers en kan vertrouwelijke informatie bevatten. Als u niet de ontvanger bent, dan mag u de inhoud van dit bericht niet bekendmaken noch kopiëren. Als u dit bericht per vergissing ontvangen heeft, gelieve er de afzender of De Post onmiddellijk van op de hoogte te brengen en het bericht vervolgens te verwijderen.

Ce message est uniquement destinĂ© aux destinataires indiquĂ©s et peut contenir des informations confidentielles. Si vous n'ĂȘtes pas le destinataire, vous ne devez pas rĂ©vĂ©ler le contenu de ce message ou en prendre copie. Si vous avez reçu ce message par erreur, veuillez en informer l'expĂ©diteur, ou La Poste immĂ©diatement, avant de le supprimer.
Received on Wed Aug 3 11:25:04 2005

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