| Summary: | Crash on startup after installation of GWT & AppEngine Plugins | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Bayard Randel <kit> | ||||
| Component: | SWT | Assignee: | Scott Kovatch <skovatch> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Silenio Quarti <Silenio_Quarti> | ||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | aniefer, christoph.stotzer, prakash, pwebster, remy.suen, skovatch | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | 3.7 M1 | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Bayard Randel
Created attachment 175489 [details]
Call stack/thread dump
attached call stack dump
What happens if you add -nosplash to the command line or eclipse.ini file? Unfortunately, the change for bug 308844 caused this because it masks a Java exception being thrown during startup. I'll try a local fix that backs that out and then I'll paste in the Java exception. Try Andrew's suggestion of -nosplash, too. It should get you around the crash. After rolling back the change in callback.c, it looks like something is swallowing/handling the Java exception because I can't get an exception dump to appear. The other interesting part is that I don't see any startup messages in the splash screen, but Eclipse still launches. Fixed in HEAD > 20100729. This is probably a 3.6.1 candidate. *** Bug 335729 has been marked as a duplicate of this bug. *** |