Bug 136710 - An internal error occurred during: "Java Search"
Summary: An internal error occurred during: "Java Search"
Status: RESOLVED DUPLICATE of bug 73784
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M4   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-13 14:26 EDT by Feng Xiang CLA
Modified: 2006-04-14 03:20 EDT (History)
1 user (show)

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 Feng Xiang CLA 2006-04-13 14:26:28 EDT 
Getting:
java.lang.StringIndexOutOfBoundsException
	at java.lang.String.substring(String.java:1015)
	at org.eclipse.jdt.internal.core.search.matching.PossibleMatch.getQualifiedName(Unknown Source)
	at org.eclipse.jdt.internal.core.search.matching.PossibleMatch.<init>(Unknown Source)
	at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(Unknown Source)
	at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.locateMatches(Unknown Source)
	at org.eclipse.jdt.core.search.SearchEngine.findMatches(Unknown Source)
	at org.eclipse.jdt.core.search.SearchEngine.search(Unknown Source)
	at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(Unknown Source)
	at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(Unknown Source)
	at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

Instructions:
- Search > Java...          
- search string "system"    
- search for "Type"         
- Limit to "All Occurrences"
- scope "Workspace"         

Testcase available upon request.

This seems to be fixed in Eclipse 3.1 but didn't find any reference of it being fixed.
Comment 1 Frederic Fusier CLA 2006-04-13 14:31:37 EDT 
Please provide test case to help me to reproduce.
Comment 2 Frederic Fusier CLA 2006-04-14 03:20:36 EDT 
In fact I retrieve the bug fixed in 3.1 stream...
Set as duplicate as I think it won't have any new update for 3.0 stream.

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