Summary: | NPE + GP switching JRE | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jared Burns <jared_burns> | ||||
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> | ||||
Status: | RESOLVED WONTFIX | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 2.0 | ||||||
Target Milestone: | 2.0 M6 | ||||||
Hardware: | Other | ||||||
OS: | Linux-Motif | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Jared Burns
2002-04-11 10:48:50 EDT
Created attachment 579 [details]
javacore.txt - the java core file generated when Eclipse crashes
Can you reproduce it ? The only possible NPE in the offending code would occur at the last line. public void addRef(char[] word) { if (indexedFile == null) { throw new IllegalStateException(); } index.addRef(indexedFile, word); <<<<<<<<<<<<<< } The index field is initialized once in the constructor of the IndexerOutput, and never reassigned. Guessing this could be a VM bug, which would also explain the GPF (a NPE should cause one). Yes, it happens to me consistently running Eclipse on IBM 1.3.1. Note that I've only seen this in my host. I haven't been able to reproduce the problem in my target Eclipse (not with a simple "Bonjour, le monde!" anyway). Does it happen too when running on a different VM ? I've only been able to reproduce it on IBM 1.3.1. Sounds like a VM bug. Can you turn off the jit and see if it still occurs ? Alternatively trying to reproduce it under the debugger would also do the trick Closing as a jit bug. |