[Bug 73] New: Get Eclipse working
| Newsgroups | gmane.comp.java.vm.sablevm.bugs |
|---|---|
| Message-ID | <[email protected]> |
http://sablevm.org/bugs/show_bug.cgi?id=73
Summary: Get Eclipse working
Product: SableVM
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: default
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
With current staging (after ProtectionDomain handling was fixed) Eclipse 3
"starts starting up". SableVM works intensively for about 20 seconds,
then simply exits w/o any trace of what happened. The behaviour is the
same with 2.0, 3.0.1 and 3.1M3.
Michael Koch says with current classpath we should get it at least start up
and show the main window.
Steve Augart, who has a lot of experience getting Eclipse working with JikesRVM
says they added the -X:vm:stackTraceOnExit and -X:vm:verboseStackTrace options
to actually see what exceptions are thrown. (the latter option prints
stack trace every time a stack trace is constructed eg. on every exception
that is created) We should probably do something similar to track what
actually the problem is.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.