Bug 78339 - NullPointerException in SecurityManager on every file save
Summary: NullPointerException in SecurityManager on every file save
Status: RESOLVED DUPLICATE of bug 66836
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.1 M4   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-10 15:58 EST by Tessa Lau CLA
Modified: 2004-11-11 11:23 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tessa Lau CLA 2004-11-10 15:58:30 EST 
I see the following stack trace dumped to the console every time I save a Java
source file in the editor:

java.lang.NullPointerException
        at java.lang.SecurityManager.checkRead(SecurityManager.java:900)
        at java.io.FileInputStream.<init>(FileInputStream.java(Inlined Compiled
Code))
        at
org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable(DiskIndex.java(Compiled
Code))
        at
org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategory(DiskIndex.java(Compiled
Code))
        at
org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategories(DiskIndex.java:352)
        at
org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith(DiskIndex.java(Compiled
Code))
        at org.eclipse.jdt.internal.core.index.Index.save(Index.java:171)
        at
org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex(IndexManager.java:506)
        at
org.eclipse.jdt.internal.core.search.indexing.SaveIndex.execute(SaveIndex.java:40)
        at
org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:361)
        at java.lang.Thread.run(Thread.java:568)
Comment 1 Olivier Thomann CLA 2004-11-10 17:54:27 EST 
Kent, this seems to be another case where the file name is null.
Comment 2 Kent Johnson CLA 2004-11-11 09:50:40 EST 
Tessa: what VM are you using?
Comment 3 Tessa Lau CLA 2004-11-11 10:17:07 EST 
IBM's 1.4.1 JDK:

java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1)
Classic VM (build 1.4.1, J2RE 1.4.1 IBM build cxia321411-20040301 (JIT enabled:
jitc))
Comment 4 Kent Johnson CLA 2004-11-11 11:23:15 EST 
This was caused by a VM bug with IBM build cxia321411-20040301 (JIT enabled: 
jitc). There are newer versions of this VM available - you should switch.

*** This bug has been marked as a duplicate of 66836 ***