Bug 6601 - Internal error when trying to extract a method
Summary: Internal error when trying to extract a method
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P1 major (vote)
Target Milestone: ---   Edit
Assignee: Dirk Baeumer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-05 12:34 EST by Dani Megert CLA
Modified: 2002-01-17 11:57 EST (History)
0 users

See Also:

Attachments
Error log file (30.06 KB, text/plain)
2001-12-05 12:36 EST, Dani Megert CLA 		no flags Details
View All 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 Dani Megert CLA 2001-12-05 12:34:58 EST 
1. In JarFileExportOperation v1.25 Select line 262 to 273 (including)
   Note: Selection includes } which does not belong to block
2. Extract method
==> Dialog pops-up: Internal Error, See error log for more details.
See attached file for the log.
Comment 1 Dani Megert CLA 2001-12-05 12:36:03 EST 
Created attachment 156 [details]
Error log file
Comment 2 Dirk Baeumer CLA 2002-01-17 11:57:04 EST 
This problem got fixed by separating the ExceptionAnalyzer from the 
StatementAnalyzer. It is now ensured that visit and endVisit calls are 
symmetrical (if you get a visit call you get an endVisit call). This wasn't the 
case in the old implementation. So when you got an endVist call without a visit 
call the stack could have been empty.

Closing