search

edwardvip / svnx

Automatically exported from code.google.com/p/svnx
0 stars 0 forks source link

Crash when double-clicking a file [with multiple svn libs installed in multiple locations] #8

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Open a repository browser on a repository
2. Browse to a file in the trunk
3. Double click said file

What is the expected output? What do you see instead?
I didn't know what to expect. I was looking for a way to get info on the file. 
Rather than doing 
something sensible, svnX crashed.

What version of the product are you using? On what operating system?
svnX 1.0.0, OS X 10.5.6.

Please provide any additional information below.

See attached crash log.

Original issue reported on code.google.com by ston...@gmail.com on 15 Apr 2009 at 6:59

Attachments:

GoogleCodeExporter commented 9 years ago 
Double-clicking should browse the item's log.
Hovering the mouse over an item will display some info.

However, I've been analysing your crash log (having rebuilt it).  Exactly which 
version of Subversion are you using & whose 
installer did you use?
It appears to have loaded svn dylibs from /usr/local/lib, /usr/lib & 
/opt/local/lib.  That doesn't look good.  It should only 
load them from /opt/subversion/lib.
Is the 'Use old parsing method' pref on or off?
Also, have you tried turning off some of the hacks you have installed?

Original comment by chris...@gmail.com on 16 Apr 2009 at 1:48

GoogleCodeExporter commented 9 years ago 
I'm running svn 1.6.1, which I installed from darwinports, using Porticus. 
You're right, though, it looks like I've 
got an unsynchronized installation, although I updated it today. "old parsing 
method" was on, so I turned it off 
and tried again. Same crash. There are quite a few "hack" in the list. It would 
be difficult to turn them all off, 
though. I'm going to reinstall svn and see if that helps.

Original comment by ston...@gmail.com on 16 Apr 2009 at 2:01

GoogleCodeExporter commented 9 years ago 
Use the svn 1.6.1 installer mentioned in the Read Me.  This is from the makers 
of Subversion, it's self contained, and I know 
it works.  Plus, the accelerated WC refresh only works with svn libs installed 
in /opt/subversion/lib.
If svnX can't find the right libs in /opt/subversion/lib it should turn 'Use 
old parsing method' back on.
However, even though it's weak linking against these libs, it appears that, 
unfortunately, OSX looks in /usr/local/lib & 
/usr/lib if it can't find them (as /opt/subversion/lib is NOT a standard 
location).  [But I've given up trying to explain this to 
the Subversion developers.]  So the problem may be that it's loading random 
(potentially incompatible) libs.  And although 
it shouldn't actually use them, just loading them may cause problems.  [OSX 
10.5 comes with svn 1.5 libs installed 
in/usr/lib.]
All this should go away if you use one of the recommended installers :-).
Ultimately, it's looks like I'll have to bite-the-bullet and find & load them 
manually.  I'll think about this for v1.1 or 1.2...

Original comment by chris...@gmail.com on 16 Apr 2009 at 3:03

GoogleCodeExporter commented 9 years ago 
I removed the darwinports version of svn and installed the "official" 1.6.1 
version. It took some fiddling, as the 
installer didn't remove existing binaries in /usr/local/bin. That may have been 
part of the problem. After 
straightening all that out, it worked.

Thanks for your help.

Original comment by ston...@gmail.com on 16 Apr 2009 at 3:02

GoogleCodeExporter commented 9 years ago

Original comment by chris...@gmail.com on 19 Apr 2009 at 12:59

GoogleCodeExporter commented 9 years ago 
"All this should go away if you use one of the recommended installers :-)."

Does that mean if I use the recommended installer for svn? I'm in 10.5.6. After
installing svnX I noticed the crash on the double click in the repository 
browser. I
then installed a recommended Subversion 1.5, using the installer from the link 
in the
help file. I pointed my preference to opt/subversion/bin, but still get the 
crash. I
tried removing the svn binaries from usr/bin. Still crash. Do I need to remove 
the
relevant svn files in usr/lib or will it help to re-install svnX?

Original comment by nitrox...@gmail.com on 30 Apr 2009 at 11:35

GoogleCodeExporter commented 9 years ago 
"Does that mean if I use the recommended installer for svn?"
Yes, one of the recommended Subversion installers.

The problem is the duplicate .dylib's, though if you have Subversion 1.5.6 
installed in /opt/subversion/ you 
should be OK, so I'm not sure why you're not.
Your preference is set to "/opt/subversion/bin" and not "opt/subversion/bin", 
isn't it?
Can you send an svnX crash log?

Reinstalling svnX will make no difference.  (Quitting & relaunching does 
everything necessary.)

Original comment by chris...@gmail.com on 1 May 2009 at 3:31

GoogleCodeExporter commented 9 years ago 
I don't know why, but I found that I had my /usr/bin preceding my 
/opt/local/bin in my 
PATH. That seems to have caused svn to find the wrong binary even after 
reinstalling 
from the approved source. Fixing the path order made it all work properly.

Original comment by ston...@gmail.com on 1 May 2009 at 2:32

GoogleCodeExporter commented 9 years ago 
I need to use subversion from MacPort with unicode_path variant.
Thus, I made links of /opt/local/bin, /opt/local/lib and /opt/local/include 
under
/opt/subversion.

This seems to work.

Original comment by kim.take...@gmail.com on 2 May 2009 at 7:39

GoogleCodeExporter commented 9 years ago 
chr..., thanks.

Hmmmm, so yes, there was a leading slash in the path, but, in looking again it 
was
back to /usr/local/bin. I really don't _think_ I did that, I specifically 
remember
putting in the /opt/subversion/bin, but then I was trying a lot of things.
I just set it again to /opt/subversion/bin, quit and then restarted and now I 
have
the double click working.

Thanks.

Original comment by nitrox...@gmail.com on 3 May 2009 at 4:41

GoogleCodeExporter commented 9 years ago 
This has been addressed in r91.

Original comment by chris...@gmail.com on 6 May 2009 at 5:17