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

Re: [Subclipse-users] Subclipse 1.4.4 Causes Segfault on OSX

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 8 Sep 2008 18:40:34 -0400

I can confirm at least one other user has had this problem. I do not
have an explanation for it at the moment. Myself and the other active
Subclipse developer both use OSX and the CollabNet 1.5.1 binaries and
do not run into this.

That bug was actually in 1.4.x and fixed in 1.5 so I thought the other
user was somehow getting a 1.4 binary loaded but that does not seem to
be the case.

You should be able to install and use SVNKit, that is what the other
user is doing.

Mark

On Mon, Sep 8, 2008 at 5:07 PM, Robert Peaslee
<rpeaslee_at_topiatechnology.com> wrote:
> Hello,
>
> I grabbed the most recent copy of Eclipse (3.4.0) and then installed
> subclipse via the update site. When trying to check a project out from our
> subversion repository (or create a project without using subversion, even),
> eclipse crashes. Running eclipse from a console and reproducing the error
> yields "Segmentation Fault" before closing.
>
> I ran eclipse through gdb following this, and got the following stack trace
> and (truncated) output:
>
> % gdb eclipse
> (gdb) run
>
> ... lots of warnings ...
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0xf1f21bc8
> [Switching to process 644 thread 0x2c903]
> 0x92f850a8 in Pool::~Pool ()
>
> (gdb) bt
> #0 0x92f850a8 in Pool::~Pool ()
> #1 0x317ee050 in SVNClient::setConfigDirectory ()
> #2 0x317fe9e4 in
> Java_org_tigris_subversion_javahl_SVNClient_setConfigDirectory ()
> #3 0x04591264 in ?? ()
> #4 0x0458aab0 in ?? ()
> #5 0x0458aab0 in ?? ()
> #6 0x0458a930 in ?? ()
> #7 0x0458ac90 in ?? ()
> #8 0x0458a9c0 in ?? ()
> #9 0x0458a9c0 in ?? ()
> #10 0x0458a9c0 in ?? ()
> #11 0x0458a9c0 in ?? ()
> #12 0x0458a9c0 in ?? ()
> #13 0x0458ae10 in ?? ()
> #14 0x0458ae10 in ?? ()
> #15 0x04588164 in ?? ()
> #16 0x9cf3dd38 in jio_snprintf ()
> #17 0x9cf4b444 in JVM_StartThread ()
> #18 0x9cf4b330 in JVM_StartThread ()
> #19 0x9cf4b2c0 in JVM_StartThread ()
> #20 0x9cf4b17c in JVM_StartThread ()
> #21 0x9ced618c in JNI_CreateJavaVM_Impl ()
> #22 0x9002bd08 in _pthread_body ()
>
> My platform is Mac OSX 10.4.11, running eclipse 3.4.0. The plugin versions
> are as follows:
> Subclipse: 1.4.4
> Subversion Client Adapter: 1.5.1
> Subversion Native Library Adapter (JavaHL): 1.5.0
>
> I looked through the bug tracker, but didn't see anything that sounds like
> it is related to this. Is this a known problem? I'm just using svn via the
> command line for now, but it would be great to have subclipse working with
> eclipse again.
>
> Thanks for any tips or existing bug references!
>
> --Robert Peaslee
> rpeaslee_at_topiatechnology.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
> For additional commands, e-mail: users-help_at_subclipse.tigris.org
>
>

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-09-09 00:40:45 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.