Community
Participate
Working Groups
Build: M9 I launched a runtime workbench and low and behold I got the following NPE upon startup. Error May 25, 2004 00:02:43.381 Background Indexer Crash Recovery java.lang.NullPointerException at java.io.DataInputStream.readUTF(DataInputStream.java:639) at java.io.DataInputStream.readUTF(DataInputStream.java:610) at org.eclipse.jdt.internal.core.index.DiskIndex.readChunk(DiskIndex.java:553) at org.eclipse.jdt.internal.core.index.DiskIndex.readAllDocumentNames (DiskIndex.java:485) at org.eclipse.jdt.internal.core.index.DiskIndex.addDocumentNames (DiskIndex.java:84) at org.eclipse.jdt.internal.core.index.Index.queryDocumentNames(Index.java:151) at org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIndex.execute (AddJarFileToIndex.java:117) at org.eclipse.jdt.internal.core.search.processing.JobManager.run (JobManager.java:367) at java.lang.Thread.run(Thread.java:534)
Which VM are you running?
Here's the code in DataInputStream that we call: public final String readUTF() throws IOException { return readUTF(this); // line 610 } public final static String readUTF(DataInput in) throws IOException { int utflen = in.readUnsignedShort(); StringBuffer str = new StringBuffer(utflen); byte bytearr [] = new byte[utflen]; int c, char2, char3; int count = 0; in.readFully(bytearr, 0, utflen); // line 639 ... } So how do we get a NPE at line 639? Its possible if the parameter 'in' is null, but its 'this' from line 610... Suspect that this is a VM JIT bug.
was using Sun's 1.4.2 at the time.
I'm going to close this since the stack trace is pretty clear that its a VM JIT problem.