Community
Participate
Working Groups
Build Identifier: 20100917-0705 After using MacPorts to update everything, including subversion-javahlbindings to 1.6.15_0, Eclipse crashes an every attempt to use SVN, even the configuration menu. The top of the error report is below. Activating the old subversion-javahlbindings @1.6.11_0 resolves the issue. Process: eclipse [91658] Path: /Applications/eclipse 3.6 64-bit/Eclipse.app/Contents/MacOS/eclipse Identifier: org.eclipse.eclipse Version: 3.6 (3.6) Code Type: X86-64 (Native) Parent Process: launchd [158] Date/Time: 2010-12-19 14:16:07.802 +0100 OS Version: Mac OS X 10.6.5 (10H574) Report Version: 6 Interval Since Last Report: 803 sec Crashes Since Last Report: 1 Per-App Interval Since Last Report: 32 sec Per-App Crashes Since Last Report: 1 Anonymous UUID: 27687175-028A-4397-88B6-654DD1A00809 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: Java information: Exception type: Bus Error (0xa) at pc=14a275eec Java VM: Java HotSpot(TM) 64-Bit Server VM (17.1-b03-307 mixed mode macosx-amd64) ...snip... Java Threads: ... snip... VM state:not at safepoint (normal execution) VM Mutex/Monitor currently owned by a thread: None ...snip heap stats... Virtual Machine Arguments: JVM Args: -Dosgi.requiredJavaVersion=1.5 -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:MaxPermSize=256m -Xms40m -Xmx384m -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts Java Command: Launcher Type: generic Physical Memory: Page Size = 4k, Total = 3968M, Free = 58M Reproducible: Always Steps to Reproduce: 1. update subversion-javahlbindings to 1.6.15_0 2. start Eclipse 3. use Subclipse
> Activating the old subversion-javahlbindings @1.6.11_0 resolves the issue. Looks that there are some incompatibility issues between Java part of version 1.6.12 in Subversive connector and binaries of version 1.6.15 or there is an issue in the binaries of version 1.6.15 itself.