...and my comment 1 above neatly ties in with the lack of HAVE_PTHREAD_MUTEX_RECURSIVE in my comment 2 above.
Thus, when svnjavahl tries to create a recursive mutex, it errors, and its error handling then blows up and SIGSEGVs. Cause seems to be that glibc has started hiding HAVE_PTHREAD_MUTEX_RECURSIVE unless you -D_XOPEN_SOURCE=500 (or greater). Adding -D_XOPEN_SOURCE=500 to debian/rules and rebuilding apache2_2.0.55-4ubuntu4 results in a working subclipse again. -- 2.0.55-4ubuntu4 update causes svn failure https://launchpad.net/bugs/62748 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
