Summary: | Eclipse Cocoa x86_64 Segmentation Fault on 10.5.6 | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Daniel Spiewak <djspiewak> |
Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | critical | ||
Priority: | P3 | CC: | cocoakevin, curtis.windatt.public, darin.eclipse, Szymon.Brandys |
Version: | 3.5 | Keywords: | needinfo |
Target Milestone: | --- | ||
Hardware: | Macintosh | ||
OS: | Mac OS X | ||
Whiteboard: |
Description
Daniel Spiewak
2008-12-20 17:14:40 EST
Important: it seems that this only happens when I force the JVM to be 1.6.0. If I allow Eclipse to choose, things work out just fine (so far). cc'ing Kevin, perhaps he can take a guess (though he may be away for Christmas). Most likey this is a dup of 251021, but there's no useful information in this bug report so we can't be sure. You need Apple's CrashReporter log to find out what was happening natively. There's already bug for the liblocalfile thing, but that navtive isn't required by Eclipse and not having it does not cause a crash. Re-assinging to resources - the stack trace shows a problem loading liblocalfile, which is related to the file system support. We need the crash reporter log file before we can diagnose any crash. Marking as worksforme. please reopen with addtional information if you have it. (In reply to comment #4) > Re-assinging to resources - the stack trace shows a problem loading > liblocalfile, which is related to the file system support. As it is stated in comment 3, "that native support isn't required by Eclipse and not having it does not cause a crash". The entry in the error log occurs always when Eclipse is not able to load the support and this is nothing unusual. In this case Eclipse just uses java.io.File. I would move it back to JDT/Debug even if it is marked as WORKSFORME so far. Reopening just to change the component. |