Summary: | [VM] Sig11 from DefaultCodeFormatterOptions | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jared Burns <jared_burns> | ||||
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||
Status: | RESOLVED INVALID | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | daniel_megert, dirk_baeumer, douglas.pollock, eclipse | ||||
Version: | 3.0 | Keywords: | vm | ||||
Target Milestone: | 3.1 M4 | ||||||
Hardware: | PC | ||||||
OS: | Linux-GTK | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Jared Burns
2004-09-13 18:10:49 EDT
The trigger is pasting in the Java editor with "Update imports on paste" enabled and having some imports in the clipboard (separate transfer type). Did you run R3.0 with jdk1.4.2_05 as well? Cannot reproduce at first sight with same VM on fedora core 2. Tried pasting around with imports, and everything works. This looks like a VM problem. I don't see what we can do. I wasn't pasting imports when this happened. The last time it happened, I copied the text: menu.add(new Separator(IDebugUIConstants.SELECT_GROUP)); menu.add(new Separator(IDebugUIConstants.BREAKPOINT_GROUP_GROUP)); menu.add(new Separator(IDebugUIConstants.REMOVE_GROUP)); out of BreakpointsView and pasted it into IDebugUIConstants. You did :-> If the Update imports option is checked paste will also add the imports (which it remembered when you copied). I see. Well, in this case there shouldn't have been any imports added because the only reference in the code I was pasting was to IDebugUIConstants... which is also the interface I was pasting into. In case it's helpful... I wrote those three lines in BreakpointsView before the referenced constants had been defined. I then copy/pasted those lines into IDebugUIConstants as a reference so I could define the constants there. Created attachment 15207 [details]
hs_err_pid4896.log
I just got another SIG 11 from Eclipse using a totally different setup. I first
got this crash on Mandrake 9.2 using JDK 1.4.2. I just got it again on Mandrake
10.1 using JDK 1.5.0.
Did you get it lately? If not, we will close as INVALID. VM JIT bug. Nope, I haven't seen it recently. VM JIT bug |