Bug 51447 - [infrastructure] NPE running JDT Core tests
Summary: [infrastructure] NPE running JDT Core tests
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M8   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-10 07:03 EST by Jerome Lanneluc CLA
Modified: 2004-03-26 05:10 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 Jerome Lanneluc CLA 2004-02-10 07:03:02 EST 
Build 20040205 + latest from THAW_402

Got the following NPE running the JDT Core tests:
java.lang.NullPointerException
	at org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable
(DiskIndex.java:558)
	at org.eclipse.jdt.internal.core.index.DiskIndex.addQueryResults
(DiskIndex.java:142)
	at org.eclipse.jdt.internal.core.index.Index.query(Index.java:137)
	at 
org.eclipse.jdt.internal.core.search.matching.TypeDeclarationPattern.queryIn
(TypeDeclarationPattern.java:188)
	at 
org.eclipse.jdt.internal.core.search.pattern.InternalSearchPattern.findIndexMatc
hes(InternalSearchPattern.java:47)
	at org.eclipse.jdt.internal.core.search.PatternSearchJob.search
(PatternSearchJob.java:119)
	at org.eclipse.jdt.internal.core.search.PatternSearchJob.execute
(PatternSearchJob.java:62)
	at 
org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob
(JobManager.java:261)
	at org.eclipse.jdt.core.search.SearchEngine.searchAllTypeNames
(SearchEngine.java:810)
	at org.eclipse.jdt.tests.core.OldSearchTests$2.run
(OldSearchTests.java:230)
	at java.lang.Thread.run(Thread.java:534)
Comment 1 Kent Johnson CLA 2004-02-17 14:12:17 EST 
Cache was flushed after first reader finished its query.

Now we use a counter.
Comment 2 Jerome Lanneluc CLA 2004-03-25 06:02:09 EST 
Not enough information to verify.
Comment 3 Jerome Lanneluc CLA 2004-03-26 05:10:18 EST 
Kent can you please verify the bug is fixed in latest integration build?