Bug 154050 - [mark occurrence] IAE in org.eclipse.jdt.internal.ui.search.MethodExitsFinder.markReferences
Summary: [mark occurrence] IAE in org.eclipse.jdt.internal.ui.search.MethodExitsFinder...
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-08-16 10:03 EDT by Benno Baumgartner CLA
Modified: 2009-08-30 02:07 EDT (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 Benno Baumgartner CLA 2006-08-16 10:03:40 EDT 
I20060810-1230

I got the following exception while editing java source code:

An internal error occurred during: "Requesting Java AST from selection".

java.lang.IllegalArgumentException
at org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:193)
at org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:1251)
at org.eclipse.jdt.internal.ui.search.MethodExitsFinder.markReferences(MethodExitsFinder.java:129)
at org.eclipse.jdt.internal.ui.search.MethodExitsFinder.perform(MethodExitsFinder.java:95)
at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.updateOccurrenceAnnotations(JavaEditor.java:3060)
at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor$7.selectionChanged(JavaEditor.java:3125)
at org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$PartListenerGroup.calculateASTandInform(SelectionListenerWithASTManager.java:163)
at org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$3.run(SelectionListenerWithASTManager.java:140)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Comment 1 Martin Aeschlimann CLA 2006-08-21 09:58:52 EDT 
This is very strange as that line is
	SimpleName name= fAST.newSimpleName("x"); //$NON-NLS-1$
and 'x' is a valid name.

Do you have this reproducable and can see in the debugger whats happening? jdt.core uses the scanner on the string and test if the returned token is an identifier
Comment 2 Benno Baumgartner CLA 2006-08-21 10:14:59 EDT 
Sorry, I can't reproduce it. It did happen only once while I did normal java source editing. 

Very strange indeed, I guess it is a concurency issue with the scanner retrieved by this.ast.scanner on line 178?
Comment 3 Denis Roy CLA 2009-08-30 02:07:36 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.