svn from subversion @1.8.8 issues "Bus error" on a 10.5.8. PPC

[udbraumann]

As has turned out during a clang-3.1 install, see ​https://trac.macports.org/ticket/43113#comment:2 a "Bus error" is being issued when trying to check out something:

$ svn --username blub co http://www2.bioinf.uni-leipzig.de/svn3/blub
Bus error

$ which svn
/opt/local/bin/svn
$ svn --version
svn, version 1.8.8 (r1568071)
   compiled Feb 26 2014, 09:10:30 on powerpc-apple-darwin9.8.0

However, the older Mac OS X version works:

$/usr/bin/svn --username blub co http://www2.bioinf.uni-leipzig.de/svn3/blub
Authentication realm: <http://www2.bioinf.uni-leipzig.de:80> blub Repository
Password for 'blub':

So as it appears, though smoothly installed from Macports, svn presently is not functional at least on my 10.5.8. PPC.

[jeremyhu (Jeremy Huddleston Sequoia)]

Please attach the crash report. I believe in Leopard these were at ~/Library/Logs/CrashReporter

[jeremyhu (Jeremy Huddleston Sequoia)]

Works fine on my Intel Leopard VM, so this is likely ppc-specific.

Leopard is not really supported any more, and ppc flavors even less so. You're probably better off working with upstream to figure out the problem and fix and then asking us to integrate the patch.

​http://subversion.tigris.org/issue-tracker.html

[jeremyhu (Jeremy Huddleston Sequoia)]

Cc Me!

[ned-deily (Ned Deily)]

FWIW, the current MacPorts svn works for me on a PPC G4 running 10.5.8 Leopard.

$ uname -a
Darwin main5.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC Power Macintosh
$ port info subversion
subversion @1.8.8 (devel)
Variants:             disable_keychain, mac_os_x_server_mod_dav_svn, mod_dav_svn, no_bdb,
                      tools, unicode_path, universal
[...]
$ /macports/bin/svn --version
svn, version 1.8.8 (r1568071)
   compiled Mar 17 2014, 15:23:41 on powerpc-apple-darwin9.8.0

Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - using serf 1.3.4
  - handles 'http' scheme
  - handles 'https' scheme

$ /macports/bin/svn co -r 156798 http://llvm.org/svn/llvm-project/libcxx/trunk libcxx
A    libcxx/lib
A    libcxx/lib/weak.exp
A    libcxx/lib/notweak.exp
[...]
A    libcxx/www/results.Windows.html
 U   libcxx
Checked out revision 156798.
$

[danielluke (Daniel J. Luke)]

I actually have a 10.5/ppc box around still, and Macports subversion also works fine for me on it. Jeremy is right that you will probably need to address this with upstream if you've actually found a bug (perhaps you're using some subversion functionality that I just don't ever use.)

[udbraumann]

Replying to jeremyhu@…:

Please attach the crash report. I believe in Leopard these were at ~/Library/Logs/CrashReporter

I could locate a crash report in this folder and have attached it. Curious what you can diagnose from it.

[jeremyhu (Jeremy Huddleston Sequoia)]

Based on the early offset in find_entry, my guess is that ht is bad. apr_hash_get just passes on to it the value it got from the caller. This makes me suspect something in libserf.

[udbraumann]

Replying to jeremyhu@…:

Based on the early offset in find_entry, my guess is that ht is bad. apr_hash_get just passes on to it the value it got from the caller. This makes me suspect something in libserf.

According to your assumption, I have first uninstalled subversion, then uninstalled serf1 and just have installed serf1 again, and then installed subversion again, and voilà, now svn works. I have no idea on how this problem was caused.

[jeremyhu (Jeremy Huddleston Sequoia)]

Odd. I'm curious what might've been different in libserf from the previous build to the new build.