Bug 107249

Summary: NullPointerException at BinaryIndexer.indexDocument()
Product: [Eclipse Project] JDT Reporter: Scott Ellis <sellis>
Component: CoreAssignee: Olivier Thomann <Olivier_Thomann>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 3.2   
Target Milestone: 3.2 M2   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Scott Ellis CLA 2005-08-17 14:30:09 EDT
We hit this npe during a run of bea internal tests. Sorry I don't have repro steps:

java.lang.NullPointerException
     [java] 	at
org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.indexDocument(BinaryIndexer.java:443)
     [java] 	at
org.eclipse.jdt.internal.core.search.JavaSearchParticipant.indexDocument(JavaSearchParticipant.java:74)
     [java] 	at
org.eclipse.jdt.internal.core.search.indexing.IndexManager.indexDocument(IndexManager.java:290)
     [java] 	at
org.eclipse.jdt.internal.core.search.indexing.IndexManager$1.execute(IndexManager.java:601)
     [java] 	at
org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:372)
     [java] 	at java.lang.Thread.run()V(Unknown Source)
Comment 1 Olivier Thomann CLA 2005-08-17 20:19:48 EDT
Could you please run your tests with debug mode on and set the .options file to
activate the tracing for indexing?
Comment 2 Olivier Thomann CLA 2005-08-18 09:07:49 EDT
What build did you use?
Comment 3 Olivier Thomann CLA 2005-08-18 09:51:19 EDT
The document path can be null, but we don't check it before we can toCharArray().
Comment 4 Olivier Thomann CLA 2005-08-18 09:59:02 EDT
Fixed and released in HEAD.
Null check has been added on this.document.getPath().
Comment 5 Maxime Daniel CLA 2005-09-20 13:02:40 EDT
Verified for 3.2 M2 on build Build id: I20050920-0010.
(By comparing released sources.)
Comment 6 Olivier Thomann CLA 2005-09-20 13:04:13 EDT
Verified in I20050920-0010 for 3.2M2