Bug 50844 - AbortCompilation thrown from Name#resolveBinding()
Summary: AbortCompilation thrown from Name#resolveBinding()
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M7   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 50891 50894 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-01-29 09:10 EST by Markus Keller CLA
Modified: 2004-02-12 13:45 EST (History)
2 users (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 Markus Keller CLA 2004-01-29 09:10:44 EST 
I20040127_1238

I was editing with 'Mark occurrences' switched on. Sorry, couldn't reproduce. I
guess it happened when I quickly moved & edited around in the file.

Error Jan 29, 2004 14:51:07.95 An internal error occurred during: "Java AST
creation".
org.eclipse.jdt.internal.compiler.problem.AbortCompilation
at
org.eclipse.jdt.core.dom.CompilationUnitResolver$3.checkCanceled(CompilationUnitResolver.java:212)
at
org.eclipse.jdt.core.dom.CompilationUnitResolver$3.findType(CompilationUnitResolver.java:219)
at
org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:94)
at
org.eclipse.jdt.internal.compiler.lookup.PackageBinding.getTypeOrPackage(PackageBinding.java:174)
at org.eclipse.jdt.internal.compiler.lookup.Scope.getTypeOrPackage(Scope.java:1399)
at org.eclipse.jdt.internal.compiler.lookup.Scope.getTypeOrPackage(Scope.java:1450)
at
org.eclipse.jdt.core.dom.DefaultBindingResolver.resolveName(DefaultBindingResolver.java:185)
at org.eclipse.jdt.core.dom.Name.resolveBinding(Name.java:89)
at
org.eclipse.jdt.internal.ui.search.OccurrencesFinder.visit(OccurrencesFinder.java:152)
at org.eclipse.jdt.core.dom.QualifiedName.accept0(QualifiedName.java:88)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:1407)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:1454)
at org.eclipse.jdt.core.dom.QualifiedName.accept0(QualifiedName.java:91)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:1407)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:1454)
at org.eclipse.jdt.core.dom.PackageDeclaration.accept0(PackageDeclaration.java:78)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:1407)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:1454)
at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:164)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:1407)
at
org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.updateOccurrenceAnnotations(JavaEditor.java:2801)
at
org.eclipse.jdt.internal.ui.javaeditor.JavaEditor$5.selectionChanged(JavaEditor.java:2825)
at
org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$PartListenerGroup.calculateASTandInform(SelectionListenerWithASTManager.java:149)
at
org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$1.run(SelectionListenerWithASTManager.java:99)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62)
Comment 1 Philipe Mulet CLA 2004-01-29 09:21:28 EST 
This exception should never be surfaced to client.
Comment 2 Jerome Lanneluc CLA 2004-01-29 13:47:24 EST 
Problem comes from the fact that the progress monitor was not cleared from the 
name environment on the first resolved. Name.resolveBinding(...) is using an 
obsolete progress monitor (that has been canceled in this case).

Changed CompilationUnitResolver.resolve(...) APIs that take a progress monitor 
to clear it when done.
Comment 3 Jerome Lanneluc CLA 2004-01-29 13:57:48 EST 
*** Bug 50894 has been marked as a duplicate of this bug. ***
Comment 4 Jerome Lanneluc CLA 2004-01-29 13:58:36 EST 
*** Bug 50891 has been marked as a duplicate of this bug. ***
Comment 5 Jerome Lanneluc CLA 2004-02-12 13:45:52 EST 
Verified for 3.0M7