Bug 119594 - [search] AIOOBE in PatternLocator
Summary: [search] AIOOBE in PatternLocator
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.2 M4   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-07 04:22 EST by Tobias Widmer CLA
Modified: 2005-12-07 16: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 Tobias Widmer CLA 2005-12-07 04:22:55 EST 
I20051206-1200

Steps to reproduce:
- Open MANIFEST.MF of org.eclipse.ltk.core.refactoring
- Goto Dependencies
- Compute Dependency Extent of org.eclipse.compare

java.lang.ArrayIndexOutOfBoundsException
at org.eclipse.jdt.internal.core.search.matching.PatternLocator.matchNameValue(PatternLocator.java:269)
at org.eclipse.jdt.internal.core.search.matching.PatternLocator.matchesName(PatternLocator.java:244)
at org.eclipse.jdt.internal.core.search.matching.TypeReferenceLocator.match(TypeReferenceLocator.java:83)
at org.eclipse.jdt.internal.core.search.matching.MatchLocatorParser.getTypeReference(MatchLocatorParser.java:311)
at org.eclipse.jdt.internal.compiler.parser.Parser.consumeClassHeaderExtends(Parser.java:1817)
at org.eclipse.jdt.internal.compiler.parser.Parser.consumeRule(Parser.java:4755)
at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:8560)
at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:8730)
at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:8695)
at org.eclipse.jdt.internal.compiler.parser.Parser.dietParse(Parser.java:7488)
at org.eclipse.jdt.internal.core.search.matching.MatchLocator.parseAndBuildBindings(MatchLocator.java:1425)
at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:928)
at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1027)
at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1145)
at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.locateMatches(JavaSearchParticipant.java:94)
at org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:206)
at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:491)
at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:532)
at org.eclipse.pde.internal.ui.search.dependencies.DependencyExtentOperation.searchForTypesUsed(DependencyExtentOperation.java:149)
at org.eclipse.pde.internal.ui.search.dependencies.DependencyExtentOperation.checkForJavaDependencies(DependencyExtentOperation.java:135)
at org.eclipse.pde.internal.ui.search.dependencies.DependencyExtentOperation.execute(DependencyExtentOperation.java:77)
at org.eclipse.pde.internal.ui.search.dependencies.DependencyExtentQuery.run(DependencyExtentQuery.java:43)
at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:94)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Comment 1 Frederic Fusier CLA 2005-12-07 07:10:37 EST 
I cannot reproduce it either in my current workspace or in a brand new one.
The only way this exception could happen is that pattern was not null but empty.
However, creating a pattern like this is not possible using current SearchPattern API methods...
Am I missing something here?
Comment 2 Frederic Fusier CLA 2005-12-07 16:23:12 EST 
Please reopen if you can provide a reproduceable test case, thx